On Wednesday, 26 June 2019 at 23:35:59 UTC, Jesse Phillips wrote:
On Wednesday, 26 June 2019 at 14:58:08 UTC, Basile B. wrote:
On Wednesday, 26 June 2019 at 09:40:06 UTC, JN wrote:
On Wednesday, 26 June 2019 at 05:38:32 UTC, Jesse Phillips
wrote:
Sometimes a good API isn't the right answer. I like getopt
as it is but I wanted a little different control. So I wrote
up an article on my work around.
https://dev.to/jessekphillips/argument-parsing-into-structure-4p4n
I have another technique for sub commands I should write
about too.
http://code.dlang.org/packages/argsd
I think we are several having written alternative getopt()
systems.
I made one too last year, it allows to write tools very nicely.
Recent example for a device flasher:
The thing is, I didn't write an alternative, mine utilizes
getopt which was the point of the article. I could build out
new functionality onto a standard API which didn't support it.
It isn't as robust as it could be.
Sorry budy, I didn't want to ruin your announce.
Hold on ;)
