Skip to content

Unordered parameters #27

@GoogleCodeExporter

Description

@GoogleCodeExporter
What steps will reproduce the problem?


What is the expected output? What do you see instead?

Currently, with required params, you have to put the param value in the 
necessary order to map it in to the correct parameter. 

Most windows systems administrators are used to specifying switches, like, 
/paramName or -paramName, without regard to order. 

Would you be willing to make nconsoler more flexible, allowing a programmer 
using nconsoler to configure it such that we can have required params that must 
be in order as it is now, but also required params where the switch is required 
and order is not relevant?

What version of the product are you using? On what operating system?

2.0

Please provide any additional information below.


Original issue reported on code.google.com by Neil.Tim...@gmail.com on 2 Sep 2011 at 5:50

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions