Unix Programming - Re: Shouldn't getopt_long() return ':' for options requiring an

This is Interesting: Free IT Magazines  
Home > Archive > Unix Programming > April 2005 > Re: Shouldn't getopt_long() return ':' for options requiring an





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Shouldn't getopt_long() return ':' for options requiring an
Måns Rullgård

2005-04-24, 2:46 pm

"Eric Lilja" <mindcooler_thisshouldberemoved@gmail.com> writes:

> Hello, consider this C program and its accompanying test script:


[...]

> As you can see, getopt_long() returns '?' for the case where the option
> requires arguments and none was supplied, I was under the impression that it
> should return ':' for that case and '?' for unknown options (it prints the
> correct diagnostic, though). Is this a bug in the implementation of
> getopt_long() on my system or are there simply different valid variants of
> the implementation?


man 3 getopt:

If the first character (following any optional '+'or '-' described
above) of optstring is a colon (':'), then getopt() returns ':' instead
of '?' to indicate a missing option argument.

--
Måns Rullgård
mru@inprovide.com
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com