|
From: Andreas L. <no...@sb...> - 2001-10-22 21:51:43
|
On Mon, 2001-10-22 at 23:33, Eric Bezault wrote: > Andreas Leitner wrote: > > > > Yep, short options are also allowed. But for short options the '=' is > > disallowed. Some apps take accept the value just with a space, > > But here '=' is not meant to separate the option from its value, > but is equivalent to the second '=' in: > > --define="name=value" > > (whose double quote characters will be removed by the > underlying shell before being passed to the application > if I remember correctly). That is correct, indeed. That actuall string received by the app would be --define=name=value > Moreover isn't the -D option the way C compilers define > preprocessor values? Correct again. But to me the -Dvar=val looks a little awked. Since the value part is variable (Dvar), it is for example not parsable via optimus. But then again, --define=name=value is awked too. Hmmm, dunno. Andreas |