From: ebachalo AT cygnus DOT com (Eric Bachalo)
Subject: Re: @file
2 Mar 1998 18:03:41 -0800
Message-ID: <3.0.5.32.19980302162624.00996230.cygnus.cygwin32.developers@pop.cygnus.com>
References: <m13eh0fxzs DOT fsf AT creche DOT cygnus DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: tromey AT cygnus DOT com
Cc: cygwin32-developers AT cygnus DOT com

>One last thing: be sure to define a quoting syntax for the contents of
>the file.  It's important to be able to pass any command-line option,
>including one containing spaces.
>
>Tom
>

Shouldn't the quoting syntax be identical to normal MS command line
quoting?  I am assuming that this functionality would only be used in the
command.com shell but I guess there is no reason not to use in a bash or
ash, etc.

I thought I would just push (insert) the file verbatim into the command
line and into the function that separates out the individual args.  The
only question I can think of now is how to deal with EOL in the file.  My
first thought would be to replace them with a space before pushing.

I was hoping to avoid path separator conversions, escape character stuff,
etc. which would then force me to have an @FILE_MODE (as opposed to the
MAKE_MODE) environment variable. :)

Best Regards,

Eric