World: r3wp

is there a neat trick to do this with less verbosity please ?
a: first parse {1/2} "/"  
b: second parse {1/2} "/"

Oh, wait until we get going on the modularization - then you'll really 
see things getting removed :)

set [a b] parse {1/2} "/"

I can send a number up to 28 with only one it or smoke signal.

it=bit

just don't make rebol require includes in every single app.  that's 
a large part of rebol's appeal.

yep Max

There will be default includes.

hey, what about my 28 to 1 lossless compression... now Paul has gone, 
someone has to keep the fire burning. :-)

But the default mechanism will be an optionnal module

Default includes: system/contexts/exports

cause frankly shaving off 100kb from rebol.exe... in an attempt to 
improve it... is like saying that life vests are in the life boats... 
but the life boats aren't accesible unless you are sinking.

just kidding

I see no point in modularisation of current R3. It is still small. 
I just wish that we do plug-ins and interfacing, tasking, in really 
good way = good for concurrency environments ...

there is a point where smaller isn't better.  it just gets annoying.

How about an on line compiling service ?  one use per month for free.

python is a good example of this.  the language as a whole  got much 
better when they integrated the datatype manipulations libs within 
the datatype classes themselves.

Pekr, just because it is modular doesn't mean that the modules won't 
be included. HTTP is handled by a module now.

in any case, I do think carl does not want rebol to become an include 
festival.

so I'm not too worried.

Actually, modules are just separated context to my mind, not really 
an astounding new features

we used context to have the same behavior in R2

Carl wants REBOL development to be manageable. Modules make that 
happen. Just ask Reichart: Qtask is built on modules.

astounding for some things yes.

Having separated contexts and being able to manage them well is a 
big deal, for security and for ease of programming.

but managing t

we can now add plugin interfaces to apps, without hackers being able 
to probe inside the main app, for example.

but managing them well is the job of the programmer, we can do dirty 
design with modules too, having them now don't prevent us to do trashes

i mean with the contexts in R2 we can do nice design too

this is a serious flaw in R2... if you want to store encryption keys 
within an application and want to provide some sort of plugin interface, 
you are pretty much fucked... people can rip your application appart, 
and there is nothing you can do about it...


a part creating a dialect, which is complicated as hell if you want 
to provide do-like syntax.

Ah, but having modules lets the work of the good programmers be protected 
from the bad programmers.

Eh but we have only good programmers here :-)

which are stymied because there are bad ones out there   ;-D

Wrong group to be saying something like that :P

hehehe

...

Mhinson don't read that

He's not the only new one - some are a lot more new than that :)

like me.

where are they hiding ?

:-) what me? bad?

Hiding from the helpful people - not a good idea...

but y

You know Brian, you can be a good programmer even without knowing 
Rebol :-)

but i agree, it's an heavy handicap to not knowing Rebol

Yup. And you can have bad moments even if you are a good programmer. 
That's what this group is for :)

nobody is perfect

I resemble that remark :)

Ladislav put nice additions to DLL interfacing ... this should make 
wrapping more flexible ...

it would be nice to be able to use the information they contain in 
the resource parts, basically auto-describing the dll themselves...
and use class members... in some way or another.