Re: lib/59828: getopt(3) GNU extension wrong behavior

["Valery Ushakov via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR lib/59828; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: lib/59828: getopt(3) GNU extension wrong behavior
Date: Wed, 10 Dec 2025 20:49:19 +0300

 On Wed, Dec 10, 2025 at 17:10:02 +0000, Simon Wollwage via gnats wrote:
 
 >  Isn't that maybe then just an issue with the wording?  The description
 >  of the extension in the man page also says that whitespace doesn't
 >  matter in this case.
 
 But the description you refer to is not the description of the
 extension.  It's the description of the "x:" example (I think Michael
 has pointed that out already):
 
      For example, an option string "x" recognizes an option â??-xâ??, and
      an option string "x:" recognizes an option and argument â??-x
      argumentâ??.  It does not matter to getopt() if a following
      argument has leading whitespace.
 
 
 Yes, it's awkward and needs to be made less confusing.
 
 -uwe