World: r3wp

I wrote the doc because we do need to solve this issue... probably 
in A99 or A100.

ok

And also, because it was a hot topic above... with many of the key 
people chatting on it. So, good time to get it finalized.

OT: It's interesting, the term "dynamic lexical scoping" produces 
no direct hits on google. Only references to dynamic or lexical scoping. 
OK, back to topic. :-)

I probably should quote that.  BTW, in REBOL definitional scoping. 
So run-time lexical.

fixed

The example just below that sentence with definitional scoping: I 
agree on that.


I ran into exactly this issue just last night in an attempt to wrap 
some function bodies in a primitive callstack mechanism (R2 code) 
so I could debug it easier. The debugging mechanism kept crashing 
there, because it ran straight through the first 'return and "returned" 
twice.


R3 of course doesn't need function scoped return for that reason, 
since I can already see the stack trace on an error, but for other 
reasons (correctness?).

Possible Return Method: Using set-word! in function spec could also 
be confused as default value for an argument. Only beginners would 
do that, I suppose.

Yes, but word, :word, and 'word are taken.

Other set-words might be catch: throw: trace: debug:

any comment towards !REBOL3 GUI wait & CPU sleep times topic? :-)

try/handle is one char shorter than try/recover :-)

alternatively:

try [block]

handle [block][error handler]

Anything shorter than handle? :-)

not sure, at least not without losing the meaning

try/do
try/on-error

Or it should be an refinement to DO?

do/on-error


But then it's a question, if TRY should be there in the first place.

*a* refinement

Carl, there is also an issue with waiting more than 597 hours in 
R2. It can be read about in the Core group. Not yet reported to RAMBO. 
I wonder if you could at least comment on it?

try/else

H: link?

WAIT issue link:
  http://www.rebol.org/aga-display-posts.r?post=r3wp157x16010

Carl, nine posts back in the Core group.

DocKimbel posting.

I see, TRY already has a refinement called /except.

oops, sunanda provides the right link, sorry.

G: no way... ah!

Works too. Great, check that one off. ;)

Docs updated.

handle: :try/except

would be cool, but maybe that's taking refinements too far. :-)

That worked at some point.

What's the quickest way to detect R3 vs R2 for hybrid scripts?

system/version/2 = 100 ?

How about allowing: clear object!


This could set all object! words to none. Would be a nice way to 
reset an object! into a clean state.

We aleady have it
>> set my-object none

Ah, cool. But it's not very obvious from the wording. IMO clear would 
be nice.

don't waste our time, do a mezz if you prefer ;-)

using clear would imply that an object is a series.

Carl is here maybe he can comment on the previous discussion regarding 
chaining.

eh ? where is that discussion ?

That was this one:

>> a: construct [b: c: 2]
== make object! [
    b: 2
    c: 2
]

On how to keep the 'b from being assigned the 2

So that it could actually be:

==make object! [
b: none
c: 2
]

Just so that we can do some dynamic building of blocks with set-words 
and pass it to construct and not worry about a set-word getting assigned 
a value from the chain.

you want optional assignement ?

yes, maybe a refinement that allows me to suppress the chaining for 
constructs

Paul, just iterate through the block before you construct it and 
whenever a set-word! is followed by another set-word! insert a none 
in between.

Yeah I could do that Anreas, just like most functions we can usually 
do some prework but thought it would offer something a bit safer 
built-in.

Write such a function and offer it to be included as mezzanine.

Any chance we can promote a feature of REBOL that looks more secure 
or performance oriented out of the box is a marketing plus in my 
opinion.