Get error for unknown options

[pheiberg]

When calling a program with an option that isn't specified, the general usage information is rendered, but no indication on what went wrong is shown. Also there is no information on the error in the IParserState. It would be very useful to be able to get information on the error.

Also see http://stackoverflow.com/q/15189849/66849

[gsscoder]

Hi,
thanks for posting the issue, @pheiberg.

Can I ask you what version are you using? Latest stable or same previous beta?

Best regards, Giacomo

[pheiberg]

I first used the beta via Nuget (one week ago) and yesterday I changed to the latest stable Nuget version.

Best regards,

Peter

On 4 mar 2013, at 06:58, Giacomo Stelluti Scala notifications@github.com wrote:

Hi,
thanks for posting the issue, @pheiberg.

Can I ask you what version are you using? Latest stable or same previous beta?

Best regards, Giacomo

—
Reply to this email directly or view it on GitHub.

[gsscoder]

@pheiberg, we're (me & contrib.) very happy you're using this project and want help use make it better reporting issues.

I've copy 'n' paste the code from S.O. (btw, the time zone got me! - someone did you already an exhaustive reply!) and you're right.

I've also to capture the value with:

[ValueList(typeof(List<string>))]
public IList<string> Values { get; set; }

But parsing still has success and the values is not captured, so this is a bug (the bad news).

The good news: it will be fixed.

A bit more (if you've time to read) to know:
In years project started as closed source in 2005, than moved codeplex 2007 ... now is also here.

The kernel complexity grown, features was added and sometimes time lacked to properly refactor internals with my current (I hope growing) level of skill! :(

Thankfully a lot a very nice devs came to help me.

Currently a lot of interesting things are happening on development branch: https://github.com/gsscoder/commandline/tree/develop-1.9.8-beta

One for all removing all side effects (first of all the implicit ones and ones potentially not benign) from the public API. (As Don Syme in its last book says side effects != intended effects).

Branch are now too distant and the new branch already solved some issue and will solve also your.

I hope this is acceptable for you and it will not make you too uncomfortable...

You'll see updates here very soon, may be during the day (here now are 7:31 !).

I'll also give instructions on unreleased beta for advanced intrepid users how want to employ it, here: https://github.com/gsscoder/commandline/wiki/Latest-Beta

Again, thanks for posting! :)

Giacomo

[gsscoder]

As said, the issue is fixed in the development branch.

Now I'll write some info on how to use it, here https://github.com/gsscoder/commandline/wiki/Latest-Beta; explaining also what risks there's using such unreleased version.

Feedback appreciated. :))

Giacomo