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

["Simon Wollwage via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Simon Wollwage <rootnode+netbsd%wollwage.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: lib/59828: getopt(3) GNU extension wrong behavior
Date: Thu, 11 Dec 2025 03:02:05 +0900

 "Valery Ushakov via gnats" <gnats-admin%NetBSD.org@localhost> writes:
 
 >  Yes, it's awkward and needs to be made less confusing.
 
 I just went and checked what OpenBSD is doing and there the manpage
 states
 
 "It does not matter to getopt() if a following argument has leading
 whitespace; except in the case where the argument is optional, denoted
 with two colons, no leading whitespace is permitted."
 
 That is less confusing (even if I think that UX might be better if the
 whitespace were allowed, but that is besides the point.
 
 Happy to rescind the submitted patch and create one to update the
 manpage to remove the confusion.