Long command line arguments do not work properly

BurntSushi / erd

Translates a plain text description of a relational database schema to a graphical entity-relationship diagram.

The Unlicense

1.8k stars 154 forks source link

Long command line arguments do not work properly #71

Closed bollafa closed 4 years ago

bollafa commented 4 years ago

Long command line arguments is chosen even though its full name hasn't been provided. Given command line argument: erd --ed Should output: unrecognized option "--ed" But instead it outputs: option "--ed" requires argument EDGE It seems that if just part of the name of the argument matches, it matches the option with the corresponding full name. ( i.e --ed matches to --edge ) I don't know whether this is intentional but I'm guessing that it isn't.

bollafa commented 4 years ago

I have checked the original GNU getopts ( haskell getOpts is just a port of it) and it is intended behaviour. Im closing this then