[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cdt-dev] command line parsing
- From: Elena Laskavaia <elaskavaia@xxxxxxx>
- Date: Mon, 09 Feb 2009 12:34:30 -0500
- Delivered-to: email@example.com
- Organization: QNX
- User-agent: Thunderbird 184.108.40.206 (X11/20090105)
In CDT we have couple places where we have to parse command line arguments,
make commands args and launch command args.
Pre-5.0 it was very inconsistent and broken (the way quotes, spaces and other non-trivial case were parsed).
I fixed it 5.0.2 and now it consistent and work as unix "shell" command line parsing works.
With one problem. Windows. On windows "\" can be used in path names and therefore cannot be used as escape character.
I forgot about that. So we have a dilemma - do we use 2 different way of escaping command line on windows and linux, or
use linux one - but with complications on windows (i.e user would have to use \\ to escape \ or unquote this) or
come up with some 3rd schema which would cover both (which I am not aware of now).
windows \ expansions bug