World: r3wp

:-)

Are you not talking Reichart ?

you did pretty good job in fact! It attracted ppl to talk about rebol!

yes, it did attract a bit of attention. I will also do some posts 
on using rebol.o inside other programs.

pekr: aahh to whom are you addressing ?

to Henrik.

this basically means that people will be able to use rebol.o and 
some rebol only decoders/parsers/readers directly in their own software 
without knowing one bit of rebol

what was the mention of deep copying of function?

make object! 10   allocates an object with enough room initially 
for 10 fields, to minimize reallocations.

get-paths

R3 now deep copies by default... but its at mezz so you can revert 
if you need.

I don't think I'im talking yet.  I will be back at 10:00a (my time) 
which is 7:00 thier time...so I assume not.

What does it deep copies? Function arguments?

path plus a colon is a path-set!  "paths are all consistent now"

the code block

Reichart. 2 hours 15 minutes from now ?

make function! spec copy/deep body

is there still subojbects sharing?

pekr, copies the body.  so we don't need to do val: copy [] all the 
time.

YEs, I can be able to go then, but I suspect they will all be gone.

max, i don't think he meant at every evaluation

Be back in 2.25 hours.

is there a class concept in rebol as one blog mentioned?

he meant at make tame

bye riechart!

Henrik, we can now remold the error message

*time

R. you might have 15 mins.. or so..

yes... gab... U are right.

Gab, please work out if I can give my talk first thing tomorrow (for 
them) basically pumping Maxim.

maxim, I didn't catch whether we can now create custom error outputs? 
such as a pretty error requester with feedback fields, etc.

ok, i'll ask

tracing...Nice.

The idea of file line numbering for debugging is a possibility for 
Rebol 3.1 maybe. (I don't care much for it myself).

anton, oh, that would be _very_ nice to have

question: can we have 16bit tuples, ie. for 16bits per channel colours, 
as used in CSS. Answer: not right away...

answer: use vector!

henrik yess. we can generate the error which is generated from rebol 
using the error object.

ha, timers :-)

Henrik, I'm not sure. I think it wouldn't be possible to always have 
an accurate answer, so if we can not rely on it, we would end u pnot 
using it.

Gabriele - is there new, more powerfull even engine in rebol, e.g. 
libevent?

anton, it's a problem currently with a function used in many places 
and you get an error inside the function (wrong value as argument). 
you can't see anything outside the function or what called it. perhaps 
the stack trace will help that, but still...

not that i know of

the new port/event system looks really great

Thankyou Carl !

Q: language plug-ins?

ah, so too late :-)

henrik, there is a Stack object!

Claps from us, please !

I would like to applause, but you guys probably can't hear it.