Jeff,
you seem to be missing the point by comparing REBOL to grep.
Suppose I wanted to write grep (or anything else) in REBOL, I'd like it
to behave just like that. I'd need a shell wrapper to hide the fact I was
running
the rebol interpreter with a script and I'd expect any and all args to the
sh
Jeff wrote:
Grep works similarly as REBOL currently does, considering
arguments preceded by - to be switches regardless of where
they are placed. For example:
Before and after args:
grep -A 3 foo * -vi
In between and after args:
grep foo -B 10 *.txt -A 20
[Garold L.
[EMAIL PROTECTED] wrote:
> Grep works similarly as REBOL currently does, considering
> arguments preceded by - to be switches regardless of where
> they are placed. For example:
>
> Before and after args:
>
> grep -A 3 foo * -vi
>
> In between and after args:
>
> gre
Howdy, Sean:
> 2) the Rebol developers (if jeff is representative) aren't
> aiming at any kind of cross platform compatibility except
> within Rebol itself, or this issue would have surfaced long
> ago. There also seems to be a bit NIHilism (Not Invented
> Here-ilism) regarding making
[EMAIL PROTECTED] wrote:
> DOing formed blocks is sort of inelegant. You're taking a
> REBOL data structure, a block, and then turning it into a
> string. By the DOing the string the interpreter actually
> turns the string back into a block of REBOL data types
> before evaluating it.
Hi,
After coding on the C64 and before hitting the bed I'll write quickly...
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
>
> Another idea that was brought up was that you could have
> more than one view of the command line args available, so
> those that want the separation of args w
>From: [EMAIL PROTECTED]
>Subject: [REBOL] Rebol's argument handling is broken Re:(3)
>Date: Wed, 12 Jul 2000 18:01:35 -0800
>
>Howdy, Jake:
>
> > 1) How many people are going to *want* an immediately DOable
> > REBOL expression?
>
> Lots of people! ;-)
agreed.
> > Maybe I'm missing
