World: r3wp

The _Official Guide_ (huge paperback) had a bracket checker as a 
worked example of using REBOL  code as data.

If anyone has easy access to a copy, perhaps they could dig it out.

I have Rebol 1.0 manual. Do you mean this?

No, the official guide as listed on this page (the link by the book 
itself no loner works):
   http://www.rebol.com/books.htmlhttp://www.rebol.com/books.html

I have it here, and found what I think Sunanda is referring to. If 
someone is really interested I'll post it.

uedit has no brace matching issues.  it works very well with REBOL 
and its fast enough to match braces  on very large parts of code 
in real time.

notepad++ does bracket matching ...

So Carl, have you come back with some proposals on the network base 
context ?

Sunanda: with the new site, please tell us what to add.  We are very 
interested, and it is easy now, to keep things updated.

Graham: make it a module.

Carl, have you seen these new plug computers?  Running Marvel ARM 
processors ...

They're going to make great REBOL appliances !

Robert mentioned it.  Let's do it!

So, R2 first ... 2.7.7 to ARM, and then R3

Probably not.  R3 first... and if that works, then R2.  R3 is built 
for portability.  R2 can be problematic.

whatever works ..

though I do want to run Cheyenne on them !

Another entry for rebolweek ... RT is porting R3 to ARM

I have one R3 question...is this bug or was it changed intentionaly 
in R3 (don't remember right now):

>> a: [[1 + 2]]
== [[1 + 2]]

this is OK:
>> do a/1
== 3

but this doesn't evaluate in R3:
>> do to-path [a 1]
== a/1

>>

I would say: intentionaly
>> do get to-path [a 1]

to-path return a quoted path

seems...

that is possible...I'd like to know the reason why it was changed 
as it is not symetric word! now...

in R2:
>> a: [[1 + 2]]
== [[1 + 2]]
>> b: [a a/1]
== [a a/1]
>> do first b
== [1 + 2]
>> do second b
== [1 + 2]
>> b: ['a 'a/1]
== ['a 'a/1]
>> do first b
== 'a
>> do second b
== 'a/1
>>


but in R3:

>> a: [[1 + 2]]
== [[1 + 2]]
>> b: [a a/1]
== [a a/1]
>> do first b
== [[1 + 2]]
>> do second b
== a/1
>> b: ['a 'a/1]
== ['a 'a/1]
>> do first b
== a
>> do second b
== 'a/1
>>


I think the R2 behaviour is more cleaner but maybe I'm missing something?

Agree now, disturbing disturbing...

a: [[1 + 2]
b: [a/1]
>> do do do do do do b/1
== a/1

really disturbing...

Can't figure if it's good or bad.

i pass...

I think it's bad.

But i'm afraid there are some drawbacks to reverse it to the R2 behavior.

Notice there is bug involved:

>> do ['a]
== a

>> do do ['a]
>> a
** Script error: a has no value

One bug is, that
do do ['a]
doesn't raise an error, when a has no value.

Yes, there is definitely something wrong in this area with R3...so 
now it doesn't look like a intentional change.

Simplest example, I think:

>> do 'a
>>

wow, looks quite broken

How do you access the arguments when passed in a command line?

r3apha myscript.r argument-list ?

probe system/options/args
probe system/script/args

says system object is protected

eh? no one knows?

no help on decode-cgi either ... 
is anyone using R3 for CGI ?

I thought it was supposed to be system/script/args.

Hmmm, same protected issue here.

checking curecode ...

known issue http://www.curecode.org/rebol3/ticket.rsp?id=628&cursor=7

or not ...

can someone with a curecode account log this as an issue pls?

btw, running with r3 -s script args
doesn't help either ...

Curecode #1430.

Graham - I've deleted the ticket because I can get the arguments 
but do get the message - it needs a bit more investigating before 
submitting the ticket.

>> probe read/string %testLaunch.r
{REBOL []

print system/options/args
print system/script/args
ask "ok?"
}


>> launch/args %testLaunch.r "text1 text2"  

Checking for rebol.r file in /Users/peter/Code/Rebol3/



System object protected

Evaluating: /Users/peter/Code/Rebol3/testLaunch.r
text1 text2

text1 text2

ok?y

== none

I don't have time to explore further at the moment. I'l try to do 
so later if nobody else has.

Peter, I'm testing from shell not using 'launch

launch simpy uses 'call to run a shell command. Anyway here is the 
ouput of the command line attempt:

Macintosh:Rebol3 peter$ ./rebol testLaunch.r "text1 text2"

Checking for rebol.r file in /Users/peter/Code/Rebol3/


System object protected

Evaluating: testLaunch.r
text1 text2
text1 text2
ok?

Macintosh:Rebol3 peter$

It might be different under windows though.