Recent changes to bugs

Incorrect parsing of integer and enum switches

Anonymous — Tue, 04 Dec 2007 07:20:22 -0000

Parsing

program.exe -n 1 -m 2

where n and m are integer switches fails. To solve this replace the line

this.valuePattern = @")((?<value>.+))";

with

this.valuePattern = @")((?<value>\S+))";

in IntSwitch.initialise()

The same goes for enum switches. The solution here is to replace

this.valuePattern = @")((?:"")(?<value>.+)(?:"")|(?<value>\S+))";

with

this.valuePattern = @")((?:"")(?<value>[^""]+)(?:"")|(?<value>\S+))";

in EnumSwitch.initialise()

Incorrect parsing of multiple string switches

Anonymous — Sat, 01 Dec 2007 12:01:39 -0000

When trying to parse

app.exe -a "aaa" -b "bbb"

the value of switch a becomes

aaa" -b "bbb

This is caused by an incorrect regex in the function initialise in class StringSwitch. The line

this.valuePattern = @")((?:"")(?<value>.+)(?:"")|(?<value>\S+))";

should be replaced with

this.valuePattern = @")((?:"")(?<value>[^""]+)(?:"")|(?<value>\S+))";

Suggestions for .NET 2.0 version

Anonymous — Mon, 08 Oct 2007 12:36:34 -0000

Some suggestions for the a .NET 2.0 version:

public static T GetOptions<T>() where T : new()
{
return GetOptions<T>(System.Environment.CommandLine);
}

public static T GetOptions<T>(string commandLine) where T : new()
{
return GetOptions<T>(commandLine, true);
}

public static T GetOptions<T>(string commandLine, bool includesProgramName) where T : new()
{
T result = new T();

CommandLineParser parser = new CommandLineParser(result);
parser.Parse(commandLine, includesProgramName);

return result;
}

public static string GetCommandLine()
{
return System.Environment.CommandLine;
}

public static string GetUsage<T>() where T : new()
{
T result = new T();

CommandLineParser parser = new CommandLineParser(result);
parser.Parse(System.Environment.CommandLine, true);

return parser.Usage;
}

public static string GetExplicitOptions<T>() where T : new()
{
T result = new T();

CommandLineParser parser = new CommandLineParser(result);
parser.Parse(System.Environment.CommandLine, true);

return parser.ExplicitOptions;
}

Incorrect constructor Parse

Anonymous — Mon, 08 Oct 2007 12:35:49 -0000

The constructor public void Parse(string[] args) does not take into account arguments containing spaces. A more correct solution is:

public void Parse(string[] args)
{
string commandLine = "";
foreach (string arg in args)
{
if (commandLine.Length > 0)
{
commandLine += " ";
}
if (!String.IsNullOrEmpty(arg) && arg.Contains(" "))
{
commandLine += "\"" + arg + "\"";
}
else
{
commandLine += arg;
}
}

Probably this leads to problems

Incorrect parsing of commandline

Anonymous — Mon, 08 Oct 2007 12:30:29 -0000

Commandlines like

"C:\path with space\program.exe" -k "text with space"

are parsed incorrectly.

The crulpit is in CommandLineParser.trimOffApplicationName. Changing the regex from

@"^(?<commandLine>("".+""|(\S)+))(?<remainder>.+)"

@"^(?<commandLine>(""(^"")+""|(\S)+))(?<remainder>.+)"

solves this problem.