World: r3wp

I think if rebol slows you down, specially with such a subtle problem 
then new programmers may not adopt it. (It will for them look buggy 
or confusing).

It can take a lot of time to find the problem of your code is not 
logic but a side effect of the language implementation.

Perhaps it could come under 'Gotchas' -- it's not a bug so much as 
a 'feature' of Rebol values and contexts?  Just as much as 'copy 
does not automatically 'copy/deep...

regarding the behaviour: I think, that it might be optimal to have 
a function like CONTEXT deep copying by default with eventual /no-copy 
refinement?

It would be *much* better to suggest the beginners to always use 
CONTEXT instead of MAKE OBJECT! and be safe IMO

I agree that hidden things like this can be dangerous, but how many 
of us have actually had a problem with it (this issue) in our applications?

I did

My view is that Carl made this a conscious choice, knowing that advanced 
users could do their own copy/deep when they need to, and it won't 
come up most of the time anyway.

We have encounter a lot of Gotchas in our development, and part of 
the reason we are slowed down many times.

Yes, but you're a special case Ladislav. :-)

We are coding cutting edge stuff. Callbacks, Sophisticated Async 
Networking and others.

well, but my suggestion regarding CONTEXT isn't very aggressive, 
is it?

Right, and I agree that this kind of thing should absolutely be documented, 
but I also think I understand why it works this way.

So if new users start to code complex applications they hit the problems 
that are not well documented and not easy to catch.

context: func [
    "Defines a unique (underived) object."
    blk [block!] "Object variables and values."
][
    make object! copy/deep blk
]

And, yes, I think it might be OK for CONTEXT to do a copy on the 
spec; I wouldn't even add the no-copy option,.

:-)

a similar issue exists for USE (use copy/deep spec) , and FUNC (solved 
by my CLOSURE)

1) Documentation is important.


2) Once you know about this behavior, which applies to most areas 
of REBOL, not just objects, you can easily solve it.

...and MAKE PROTOTYPE-OBJECT SPEC

the CLOSURE case is not that easy

But closures are a very advanced concept; normal people will never 
even hear the term.

The biggest risk I see for normal people, is when you're doing things 
like deserializing objects and such.

wrong - everyone is going to need closures once writing async code

Closures are usefull for concurrent programming which is needed in 
async schemes.

But, again, that is an advanced concept. If only 10 people in the 
world understand it, that's OK, as long as they hide those details 
so it just works, magically, for the rest of us. :-)

but once the core becomes async, everyone will have to adjust to 
it

Why? I don't have to know anything about how REBOL's GC works, do 
I? If *everyone* has to understand and adjust to async, and if even 
10% of people need to know how closures work, that would be a tragedy.

you do not *need* to know how closures work, the only thing you need 
to know is, that when you use a closure instead of a function, some 
bugs vanish

If we are pushing rebol to be capable of handling more and more problem 
spaces, then we need more powerful constructs and excellent docs.

more powerful constructs
, like what? (kind of playing Devil's Advocate here)

closure, associative arrays, construct with deep copy, load on values 
that don't exist in system object, others. Some of the bugs that 
have been fixed are due to our need for more power, stable and predictable 
interpreter.

stable and predictable; I'm all for that. Beyond the LOAD issue, 
we can do all that, right?

Yes, we can patch rebol and fixed ourselves, but we should remove 
some "surprises" like making CONSTRUCT safe.

It's really a question of default behaviors, right? (making sure 
we're talking about the same thing)  My concern is that, by making 
more things "safe" at the native level, we may create more issues 
than we solve.

I had another issue with the behaviour of APPEND which is different 
for block! hash! than from list! and it is a side effect of INSERT 
and REMOVE
APPEND b: make block! [] [v1 v2] head? b ;== true
APPEND l: make list! [] [v1 v2] head? l ;== false

I don't know how many of this type of examples are there, but is 
quite annoying to debug these side effects.

that has nothing to do with append - that has to do with list!s.

I would say that's a bug in APPEND, because of the way the doc-string 
is worded.

l: append ... would work

but append l ... does NOT change the word 'l

actually, it isn't a bug and it is almost impossible to change, but 
it may need a documentation

We need more consistency. I discuss the APPEND issue extensively 
with Ladislav, and it is about docs and side effects. What I fear 
is the explosing of exceptions.

could be changed, but only for the "head" case, if the list head 
was a special node (like Exec's double linked lists)

I would like also to be able to implement our own types! and be able 
to overload some words. So that an implementation of associative 
arrays can work look like [make aa! 10] instead of [aa/make 10]

Any opposition on proposing the change to CONSTRUCT?

Do you mean CONTEXT?

Sorry CONTEXT.

You can propose it. I'm happy to let Carl decide. I wonder if it 
might cause some confusion as it won't be an exact replacement for 
make object!, which it's just a shortcut for. It could break code 
and change behavior if substituted.

I am quite curious if it breaks really would break some code