Re: Running a standalone script on MS windows (blech!) callable from SAS

[forkandwait]

Martin Helm <martin <at> mhelm.de> writes:

> What about writting a batch file which runs octave with the script?
> It would simply contain
> 
> octave myscript.m

So, this basically works, but there is a weird issue with argv().  

I call

FULLPAPTH\octave --quiet FULLPATH\myscript.m

When called with no argv data for myscript.m (just like above), argv() returns 
{"--quiet", "myscript.m"}.  When called 

FULLPAPTH\octave --quiet FULLPATH\myscript.m INPUT

argv() returns {"INPUT"}

This seems, um, bad.

Also -- is there a way to turn off the warning about "mark_as_command will be
removed..."?  Maybe this is being used by the MINGW set up,..?

Thanks again.