Quote:

again.
fixing this issue is rather simple.
instead of using the args parsed for you, parse them yourself from the raw commandline.



It is a work-around, but I don't think that it's a good long term solution to say 'using $var="VALUE" on the command line doesn't always work as you'd expect so you're better off parsing the line yourself'. Much better to fix '$var="VALUE"' so that it always works as expected.

Quote:

and richie, not sure I understand your flaming of MS here.


Hah! Having had to put up with doubling speech marks, using ^ as an escape and various other unspeakable and changing kludges over the years, it's no surprise that the goal-posts have been moved again. I appreciate that some of this nastiness is down to the command line interpreter.

Quote:

you just posted a while ago that same issue is there with gcc.
last time I checked, it's not MS compiler.


Correct. However it will of course use standard Windows code and libraries including start-up code, and that is where the problem lies.