Timeline for The discrimination between short and long option is only `-`?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2016 at 11:59 | history | edited | schily | CC BY-SA 3.0 | typo |
| Jan 26, 2016 at 16:26 | history | edited | schily | CC BY-SA 3.0 | typo |
| Jan 26, 2016 at 16:15 | comment | added | muru | Nope. In go, each option is set up individually, and has an associated variable and type (so that conversion is also done automatically). And you can have one or two leading hyphens for long options. | |
| Jan 26, 2016 at 16:12 | comment | added | schily | go does not seem to support a format string similar to what getargs() offers. | |
| Jan 26, 2016 at 16:10 | history | edited | schily | CC BY-SA 3.0 | mention getargs.c |
| Jan 26, 2016 at 14:32 | comment | added | muru | Go's standard option parsing works very like UNOS's, so I guess that's where Go got its inspiration. | |
| Jan 26, 2016 at 14:15 | history | edited | schily | CC BY-SA 3.0 | add Solaris getopts() enhancements |
| Jan 26, 2016 at 14:09 | history | answered | schily | CC BY-SA 3.0 |