[Omake] Command syntax

[Aleksey Nogin]

On 12.06.2006 07:07, Benjamin Pierce wrote:

> According to my reading of the documentation...
[...]
> ... this should be a legal shell command:
> 
>> foobar:
>>   chmod -w foo
> 
> 
> But it fails in a surprising and (until I realized what must be  
> happening) puzzling way:
> 
>> omake foobar
>> *** omake: reading OMakefiles
>> *** omake: finished reading OMakefiles (0.4 sec)
>> - build . foobar
>> + chmod -w foo
>> *** omake error:
>>    Lm_arg.BogusArg("No such option: -w")
> 
> 
> Is this a bug in OMake, the documentation, or my brain?

The issue is that the built-in commands often report their errors using 
the "default" "*** omake error: ..." syntax. Basically, the "chmod -w 
foo" does get executed, and then it prints the above error message while 
trying to parse its command line.

P.S. BTW, in 0.9.8 we made it explicit when a shell command is evaluated 
internally:

*** omake: reading OMakefiles
*** omake: finished reading OMakefiles (0.3 sec)
- build . foobar
+ Shell.chmod(-w foo)
*** omake error:
    Lm_arg.BogusArg("No such option: -w")


-- 
Aleksey Nogin

Home Page: http://nogin.org/
E-Mail: nogin at cs.caltech.edu (office), aleksey at nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200