Re: open and backslashes...

From: Jeff Godfrey (jeff_godfrey_at_pobox.com)
Date: 03/25/05 

Date: Fri, 25 Mar 2005 14:05:44 -0600

"Don Porter" <dgp@email.nist.gov> wrote in message
news:slrnd48r3g.sv5.dgp@clover.cam.nist.gov...
> Jeff Godfrey wrote:
>> Agreed. That would be ideal. Unfortunately, the command line string is a
>> user-supplied value, and one that I really don't have much control
>> over...
>
> Oh, it's a parsing problem then?

Precisely. It's an problem of validating / correcting a User-supplied
command line for an executable. Said command line may or may not contain
backslashes in the actual exe path, and in one or more of the arguments for
the executable itself. The trick is to resolve the entire mess into
something that's acceptable to "open |" and yet doesn't break any of the
arguments destined for the executable itself...

> [auto_exe***] should be able to help you find the prefix
> of that line that corresponds to an executable program.

Hmmm... That doesn't appear to have helped, because:

1. I need to break out the "exe" name from the command line string prior to
passing it to auto_exe***
2. auto_exe*** seems to need *forward* slashes to work.

If I had both of those solved cleanly, I don't really need auto_exe***...
;^)

Thanks,

Jeff