Mail Archives: cygwin/2008/08/30/15:55:52
On Sat, Aug 30, 2008 at 12:00:14AM -0700, Stephan Mueller wrote:
><offtopic>
>Yes, it's awful, but the batch file isn't totally at a loss. If, in
>the batch file, you refer to parameters %1 %2 etc., as you've
>discovered, the parsing treats equals signs (and semicolons, and
>perhaps others; I forget) as spaces. But, if you refer to %*, you can
>get the whole original command line, unmolested, inside the batch file.
>At worst, you can tokenize it yourself (with the cryptic but
>powerful-enough batch 'for' command, perhaps), but at best, you can
>just use it as is and pass it to your compiler.
>
>At one time, and perhaps still, Microsoft compilers support(ed) using #
>in place of = on the command line: -DSOMETHING#AVALUE. I'm willing to
>bet it was to work around this misfeature of batch.
></offtopic>
This is all an argument for using Cygwin the way it was supposed to be
used - there are no .bat files on UNIX. Use shell scripts instead.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -