World: r3wp

So it really does just save typing.

:)

Note it only only does copy/deep of series. Objects are still referenced, 
so you still need the does [make proto []].

Some say that developers are born with a finite number of key strokes... 
once they are used up, that is the end.

hmm, it's a bug no ?

or a missing feature, as you wish

No, I can see the value of only copying series. You don't usually 
want to copy objects - it's not as safe.

ok i do 10 push-ups

I need more excercise anyways :)

Spelling doesn't count if it's not code though :)

every single day (and often a few times that day):

- I open up a rebol console from quick-launch bar in windows (taking 
about 0.1 sec to appear)
- type help 'some-func 
- test the 'some-func with some-data I'm using. 
- close the console.  


overall it takes about a few seconds, to do a unit test of something 
I'm adding.
 no bloat,  no dangling window.

python offers something similar... but:
- python takes anywhere from 3-10 secs on load.  

- then you have to know in what lib the most basic function is (alread 
half as usefull) 
- the console itself is really bad, 
- previous commands browsing is really stupid

- having to type so much more code to get the simplest function test 
going is a pain
- in the end, its a non-feature.

I leave a R2 and R3 console open full-time while I'm working. It 
helps to have R3 open too since I don't always remember how much 
of R3 I've backported to R2, so sometimes I remember a function that 
doesn't exist in R2.

I found a cosmetic bug in the console

I was just pointing out that rebol is sooo fast to launch that you 
can close it and its not a pain... I easily get up to 10-15 windows 
open at a time, and when you've got half of them as rebol consoles, 
its easier not to guess which one is the help window  :-)

impossible... the console is *perfect*   ;-)

i have 3 R3 consoles (one for the chat, on for test, one for... i 
don't remember)
I have 1 R2 console for testing

maxim, it's amazing that R3 is even faster at launching.

Text mode :)

well.. Obviously, Carl keeps removing stuff from REBOL... just ask 
steeve   ;-)

nah, it's just that Carl has secretly figured out how to do random 
compression.

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.