Jonathan, I'd nod my head in agreement to that last line it is annoying, but in a=20 pleasant REBOL kind of way. :)
We still have to wait a few more sleeps, but there have been promises made= =20 about simplifying Programming In The Large with REBOL version 3, and multip= le=20 scripts in a project with argument passing will hopefully get a good work=20 over. As well as making R3 more shell scriptable. I look forward to a day= =20 where I can log into up my GNU/Linux box with /usr/bin/rebol as the shell, but for now those are just hopes and dreams, realistic hopes and dreams, bu= t=20 still a few more sleeps before coming to grips with the true potential of R= 3. R2 is capable of doing almost everything, but it usually involves=20 experimenting to make things fit and you have approach each problem knowing= =20 that the solution you think will work my not be the solution of best fit. Cheers, Brian=20 On Sunday 29 July 2007 03:18, Jonathan Kelly wrote: > Its best to access system/options/args except that "do/args" only > populates the system/script/args. =A0The script has to have special code > to deal with whether it's being called directly, or from another script, > or you HAVE to use system/script/args, as that's the only consistent > data element. Then again, it doesn't work at all if you "load" the > script and then "do/args" it. I'd call it a bug, but if it's argued not > to be, it surely breaks the "simple" design philosophy. > > Anyway, it annoys me. -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
