AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add a comment with links to proper command line parsing rules.

Browse Source 
No real changes, just added a comment with links to the descriptions of the
correct rules that we should use in ConvertStringToArgs().

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@73747 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin 2013-03-31 01:11:47 +00:00
parent 6150a29606
commit 8dd4c6113d
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
src/common/cmdline.cpp
View File

@ -1377,6 +1377,23 @@ static wxString GetLongOptionName(wxString::const_iterator p,
Windows conventions for the command line handling, not Unix ones. For
instance, backslash is not special except when it precedes double quote when
it does quote it.
TODO: Rewrite this to follow the even more complicated rule used by Windows
CommandLineToArgv():
* A string of backslashes not followed by a quotation mark has no special
meaning.
* An even number of backslashes followed by a quotation mark is treated as
pairs of protected backslashes, followed by a word terminator.
* An odd number of backslashes followed by a quotation mark is treated as
pairs of protected backslashes, followed by a protected quotation mark.
See http://blogs.msdn.com/b/oldnewthing/archive/2010/09/17/10063629.aspx
It could also be useful to provide a converse function which is also
non-trivial, see
http://blogs.msdn.com/b/twistylittlepassagesallalike/archive/2011/04/23/everyone-quotes-arguments-the-wrong-way.aspx
*/
/* static */