openbsd/src/lib/libc/stdlib/getopt_long.3, branch OPENBSD_7_9_BASE

.Li -> .Vt where appropriate;

2022-09-11T06:38:11+00:00

from josiah frentsos, tweaked by schwarze ok schwarze

refer to longindex as an argument, not a field;

2022-01-06T18:58:24+00:00

from uwe@netbsd -r1.22 ok millert

For open/openat, if the flags parameter does not contain O_CREAT, the

2021-10-24T21:24:20+00:00

3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert

Document how to make getopt_long(3) process arguments in order and stop

2020-01-13T18:05:10+00:00

at the first non-option argument. I had to read source code to figure it out.

Follow style(9) and drop lint /* NOTREACHED */ annotations from

2016-01-04T19:43:13+00:00

the examples. Diff from Juuso Lapinlampi < wub () partyvan ! eu >, thanks! ok schwarze@

Use the fancy .In macro for includes. From Jan Klemkow. ok jmc schwarze

2013-06-05T03:39:23+00:00

tweak for clarity, ok millert@, jmc@

2011-03-21T13:41:50+00:00

Fix PR 6267: recheck POSIXLY_CORRECT each time getopt_long() starts a new

2011-03-05T22:10:11+00:00

argv and don't suppress the handling of leading '-' in optstring when POSIXLY_CORRECT is set. Based on patch from Eric Blake. ok and manpage update from millert@, manpage ok jmc@

Correctly escape a literal colon in an enclosure;

2011-01-24T01:50:25+00:00

the \: roff escape is an optional line break.

more wacky macro fixing;

2010-09-19T22:22:13+00:00