World: r3wp

Andreas, I like those :)

Steeve, the bias of using an ambiguous language like English to discuss 
a precise topic :(

+1

Andreas, yes, those terms existed for quite some time....

Those are my preferred terms as well.

what is the fastest way to deep copy a large object?

Try:
>> new: make object! third <object>

it does not work for nested objects.

Then, you probably have to write an recursive function that will 
copy all nested objects. Have you looked for such function on rebol.org 
and in power-mezz package?

I need special functionality, so I will write my own.

Turns out it's far too slow.

object creation/duplication in Rebol is very slow, the binding just 
kills it.  can you re-build your system with block?

(or parts of it ?)

I'm going to copy the parts I need instead.

>> select [1 2 2 3] 2
== 2
>> select/skip [1 2 2 3] 2 2
== [3]

Why the second returns a block?

iirc this is known behavior/issue in R2...has been unified in R3

Oldes, try it with a skip of 3 or 4 to see why a block is returned. 
Not very handy in the 2 case though... but I guess there was a desire 
to avoid special cases.

/skip return records
i.e.  
>> select/skip [1 2 3 4 5 6] 4 3
== [5 6]

I'm just missing MAP! in R2:

>> m: make map! [1 2 2 3]
== make map! [
    1 2
    2 3
]

>> select m 2
== 3

Fortunately the /skip in SELECT/skip is ignored for map! in R3, so 
you can just use it in both.

Darn the R2 version does a copy/part. Silly differences.

in R2:
>> make map! []
== make hash! []
>> m: make map! [1 2 2 3]
== make hash! [1 2 2 3]
>> select m 2
== 2

which is not what I woul expect

Seems like map! is just redirected to hash! . Can be seen with
	? datatype!
, and that's probably confusing, as they behave differently.

Can also be seen with
	? "map!"

>> source to-map
to-map: func [value][to hash! :value]

Is there an official documentation of
	make struct! ...
?

Is there documentation of constructs like #[none] ?

http://www.rebol.com/docs/sdkug.html

see "External Library Interface"

There it was, thanks!

I don't see doc about C datatypes in struct! spec block. I guess, 
it's the same rules as in routine spec block?

Example, where I use the C datatype, int:
	>> s: make struct! [i [int]] [42]

About constructs, off my head I have:
	#[none] #[true] #[false]

Are there others?

>> #[binary! "abc"]
== #{616263}
>> #[bitset! #{010203}]
== make bitset! #{010203}
>> #[block! [1 2 3 4] 3]
== [3 4]
>> #[email! "something"]
== something
>> #[file! "something"]
== %something
>> #[function! [a b] [a + b]]
** Script Error: none is missing its a argument
** Near: func [a b][a + b]

... and so on

Is this documented anywhere?

Perhaps not, geomol. See this cc thread:
   http://curecode.org/rebol3/ticket.rsp?id=941

The "serialized" word is very inappropriate, e.g.:

    /all "Mold in serialized format"


does not say anything at all, since the format without the /ALL refinement 
is serialized as well (it is a text string).

Some other inappropriate notions:

   "serialized constructors", when used for #[none]


e.g. is a very unfortunate notion, since it is not a constructor 
(=a special function), not to mention, that it surely is not a serialization 
of such a function.

(my notes apply to the text of the curecode discussion to the above 
mentioned ticket)

Fortunately, according to Carl's note, the correct notion for the 
#[none] and similar formats seems to be:

    "specially escaped format"

Does serialization not imply there is a reverse action for it? Only 
MOLD/ALL will allow that.

Hmm, that looks like a proper objection, but it does not take into 
account, that e.g.

    123


is a result of both MOLD as well as MOLD/ALL and it surely is serialized, 
while e.g.

    #[none]


is not just "serialized", it is a "specially escaped format", as 
noted by Carl

Moreover, MOLD usually does preserve REBOL code in the sense, that 
you get the same program when loading the result of MOLD more often 
than not.

While even MOLD/ALL does not look "reversible enough" for some functions, 
objects, etc.

For all the above reasons, it is much better to call the #[none] 
and the likes "specially escaped format" rather than "serialized 
constructors".

The unfortunate thing is, that there is the MOLD vs. MOLD/ALL ambiguity, 
which confuses every beginner exactly because when they encounter

    none


they usually think it is a REBOL value of the type NONE!, which may 
mislead them in many cases

do we have both MOLD and MOLD/ALL for performance reasons?

I do not think there are performance reasons for that.

why do we then have MOLD and FORM?

rather: why do we have MOLD at all? I'm not sure we can say that 
it preserves REBOL code, because, surely, MOLD/ALL preserves more 
of it.

For example, if MOLD/ALL were used to display the result of an expression 
we would obtain:

    none
    == #[none]

, which would be less confusing than

    none
    == none