Thanks for the reply Steve
On Sunday, 9 August 2020 at 12:20:16 UTC, Steven Schveighoffer
wrote:
2. If your optional parameters are not tied to the option
itself, then don't accept them via getopt. In other words, if
`hashtrack filter` is supposed to be valid, then filter isn't
an option afte
On 8/8/20 7:58 PM, Hassan wrote:
Hello
I'm trying to get getopt to recognize an argument that may or may not
take a value. Here's an example :
../hashtrack --list
../hashtrack --list filter
The problem is that if I point list to a string variable, the first call
fails with "Missing value fo
Hello
I'm trying to get getopt to recognize an argument that may or may
not take a value. Here's an example :
./hashtrack --list
./hashtrack --list filter
The problem is that if I point list to a string variable, the
first call fails with "Missing value for argument --list".
I tried having
