World: r3wp

Steeve: When you say the data are saved as Rebol values does that 
mean they are saved as molded Rebol values?

Will, I haven't done a lot of work for R2 lately - only Anton has, 
afaik, and we haven't even gone over his submissions yet. After the 
R3 public release happens and the next DevBase is running we can 
work on a R2 release. More backports I hope :)

Peter, yes it's molded values.

Thanks for the status, Brian

Nope, still doesn't work.
>> write %blah to-binary "hello^/rebol [] print 1"
>> do %blah
** syntax error: Script is missing a REBOL header: hello

** Note: use WHY? for more about this error

Strange again, i do my script as-is and it works...

SCRIPT? still doesn't work properly, because the native FIND-SCRIPT 
it calls still doesn't work properly.

Look again: Is the script you are doing the same as the one you posted, 
including the docs at the top?

I like WHY? idea so much, dunno why :-) It looks so natural/simplistic 
...

y

yep Mister Biran, it's the same

* Brian, sorry

Weird. Do you use a different LOAD than the one in R3 by default, 
or a different SCRIPT?

ahah no, i save my scripts in ANSI format

I meant the function SCRIPT? not your text encoding :)

Question for the community:

It has been a long time since REBOL 2 was first released. Is it finally 
OK to remove the ELSE native from R3?

ELSE hasn't been used since R1, and has thrown an error since the 
first R2 betas. Can we get rid of it now?

yes !!!! got it !!!
REBOL [] must be in uppercase it not, it failes.
Give me a medal Brian

*if not

Cool, I'll update the ticket.

it's not a bug Brian, onl

If the user doesn''t write REBOL in uppercase, he must be fired... 
;-)

We have a lot of hot programmers in the community... :)

(oh my god !!! i have not anymore cigarettes)

brb

The horror!

(ouf i'm saved, i have cigarettes and whisky)

f: func [n] [if n = 1 [print 1] else [print 0]]
f 2
Re else;
** Script Error: else has no value
vs
** Script Error: else is obsolete. Use the EITHER function


Second one far better for new to REBOL people imho.  The'll only 
do the second case twice in a career, the first may have them scratching 
head for 10 minutes and giving this new REBOL thing the boot.

Lies, damned lies, and statistics
 :

525 tickets on CureCode Rebol3
41 dimissed
2 completed
482 outstanding

Though 320 are marked as tested.

The 2 completed are documentation requests. The reason the tested 
and dismissed ones are not marked completed is because I don't know 
the policy for making that distinction.

Tested=>Completed : I guess that once the fix (or new feature) is 
released to users, it should be marked as completed.

It would be grest if you could get the tested requests marked as 
completed as the stats give such a bad false impression.

Doc's definition sounds good with the proviso that the status can 
be reverted if the user finds the bug hasn't been fixed.

Btw, ticket should be closed by the emitter once the fix is released. 
If the user don't do that after a given period (let say 1 or 2 weeks, 
one of CC's admin or developers can do that instead).

BrianH : yes please remove "else"

virtual block looks very cool !   how were you able to use the same 
words insert,copy,etc.. on new datatype (I suppose without changing 
the initial insert functions) .. can this be done in rebol, I thought 
it's not possible but being able to define something like generic 
words on custom datatypes would be very important function? hm.. 
while I am at it... I realized I have no idea about what datatypes 
in rebol are and if one can make it's own..

Janko, because the supported functions like COPY works on ports, 
and virtual blocks is a port scheme, customizing how COPY works with 
that specific scheme.

Ahaa.. I saw ports and schemes mentioned and that you can define 
your own, but still have no idea what they are, will need to read 
more about it..

rebol is both very small and very big at the same time

(in a good way)

so it's not a new datatype, but a new scheme for port!.

yes, I realized .. that's why I said big.. usually there are functions 
and variables, here are so many things, dialects, schemes .. etc 
:)

I think you can figure out how it works by reading Steeves code. 
It's quite simple.

that link doesn't work for me , and I also don't have r3 to test 
it

I saw some tutorial about creating new "protoco handler" .. or is 
that a third thing?

it should be the same thing

if you read about ports in the wiki, they'll give a fair explanation 
of how they work.

it's the same reason you can use READ on files, HTTP, FTP, etc.

aha yes.. this is interesting concept .. I was alredy thinking about 
it when I was using pop:// protocol (carl probably realized that 
most "communication" can be abstracted in means on operating on serries)..