Reacting to shell commands?

Dar Scott dsc at swcp.com
Tue Oct 17 15:15:10 EDT 2006


On Oct 17, 2006, at 11:24 AM, Mark Wieder wrote:

> Tuesday, October 17, 2006, 9:27:19 AM, you wrote:
>
>> A couple years ago this did not work right.  Has this been fixed?
>
> Do you remember what in particular wasn't working? I've been using
> these without too many problems - the things I've run into are the
> chars that get swallowed by the engine. I BZed them, but I misremember
> at the moment exactly what chars get eaten. (-p?)

At one time, long ago, before Bugzilla came to the Revolution, a  
simple command line (past $0) would all go into $1 unless there were  
quotes and then Windows quoting methods were ignored and some info  
got lost.  At the time Scott Raney and Kevin Miller felt this was not  
a bug and that this behavior was required because of a bug in Windows.

So, there were two problems.  First one had to test the platform and  
either look at $n on OS X or parse $1 on Windows.  The other problem  
is that quotes were dropped and had to be reconstructed with  
heuristics.  The latter could work only if there were only switch  
parameters or the object went before all switch parameters.  So even  
then, parsing $1 could get complicated.  Some command-line syntax  
definitions required the use of an external.

I had a vague memory of other quoting problems, perhaps with a  
literal quote in the command line.  I don't remember how Windows does  
that.

This is not a problem on OS X.

Dar





More information about the Use-livecode mailing list