> As far as I can tell the only thing gained from using getopt is handling
> vipw --
> as vipw takes no flags or arguments, is not intended for non-interactive
> use, and is not POSIX, I don't see a reason -- should be handled. If
> anyone prefers proper handling of -- perhaps
> if (!( ar
Matthew Martin writes:
> As far as I can tell the only thing gained from using getopt is handling
> vipw --
> as vipw takes no flags or arguments, is not intended for non-interactive
> use, and is not POSIX, I don't see a reason -- should be handled.
I don't see a reason not to handle -- as
As far as I can tell the only thing gained from using getopt is handling
vipw --
as vipw takes no flags or arguments, is not intended for non-interactive
use, and is not POSIX, I don't see a reason -- should be handled. If
anyone prefers proper handling of -- perhaps
if (!( argc == 1 ||
