Re: using quotes in command-line-commands under Windows

[David Kastrup]

Eluze <address@hidden> writes:

> David Kastrup <dak <at> gnu.org> writes:
>> 
>> It is also conceivable that this depends on the startup stub of whatever
>> compiler you happened to be using.
>> 
>> I know why I don't do Windows.
>> 
> anything works:
>
> -dpoint-and-click=#f
> -dpoint-and-click="#f"
> -d"point-and-click=#f"
> -"dpoint-and-click=#f"
> "-dpoint-and-click=#f"
>
> who's gonna tell us why?

As I said: it might depend on the startup stub of whatever compiler you
happened to be using.

Since C expects a certain amount of command line preparation
traditionally done by the shell that is passed through exec, and since
Windows, at its heart, did not use to have prepared arguments but just a
single humongous line, this was traditionally the task of the startup
stub called by the operating system, and in itself calling main with the
prepared arguments.

I am employing "traditionally" here in the usual sense it is used in
Windows, namely as "this was a terrible idea 20 years ago already, so
let's keep it".

-- 
David Kastrup