3 ms·
I'd also add that CommandLineToArgvW doesn't do exactly the same thing that the C runtime does to parse arguments. They used to be the same but the C runtime wa
by ChrisSD 6y ago
I'd also add that CommandLineToArgvW doesn't do exactly the same thing that the C runtime does to parse arguments. They used to be the same but the C runtime was tweaked in 2008 whereas CommandLineToArgvW was kept the same for backwards compatibility. See http://daviddeley.com/autohotkey/parameters/parameters.htm#WINCRULESREPH http://daviddeley.com/autohotkey/parameters/parameters.htm#W...
- Varriount 6y agoHuh. Wouldn't this have caused inter-operability problems for programs that spawn other processes?
- ChrisSD 6y agoPresumably they would have tested extensively for regressions. But I'm not sure what would break that wasn't already broken. It was an obscure undocumented case that was not intuitive.
- gpvos 6y agoOther links with code to parse/construct command lines: - https://web.archive.org/web/20200128073602/http://www.windowsinspired.com/how-a-windows-programs-splits-its-command-line-into-individual-arguments/ https://web.archive.org/web/20200128073602/http://www.window... - https://web.archive.org/web/20191119112915/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/ https://web.archive.org/web/20191119112915/https://blogs.msd...