On 9/27/07, <b class="gmail_sendername">Nicholas Bastin</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 9/22/07, <a href="mailto:firstname.lastname@example.org">email@example.com</a> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>> argc/argv does not exist on Windows (that you seem to see it<br>> anyway is an illusion), and if it did exist, it would be characters,
<br>> not bytes.<br><br>Of course it exists on Windows. argc/argv are defined by the C<br>standard, and say what you will about Windows, but it has a conforming<br>implementation. argv exists on Windows exactly the way the C standard
<br>requires it - as an array of null terminated "strings". It's left as<br>an exercise to people with more time than I to argue about the<br>definition of the term 'string' in the C standard (since the standard
<br>itself is silent on the issue).</blockquote><div><br>The entry point of a Windows application is WinMain, not main; you can create a console-only standard C application if you'd like, but its not a Windows program. Python apps are Windows programs even if they have a console attached. And the WinMain function passes the entire command line as a single char* with no breaking or parsing of any kind.