This issue is under discussion again in the C23 ballot resolution. The
current POSIX
standard has the type for tv_nsec as a long, and there is, to my knowledge,
no
proposal from the Austin Group to change it. Geoff's suggestion that
perhaps
changing this type might be acceptable is being taken as
Note that a flexible array member is not the same thing as a variable
length array, and although both entered the standard in C99, previous
versions allowed the FAM to be specified as an array of length 0.
The C standard notes that:
> In most situations, the flexible array member is ignored. In
Hi Mark;
please feel free to ask on this list initially. Between us, we should be
able to answer if it is (a), (b), or (c). In general, the POSIX shell was
modeled on ksh88, but a few small changes were incorporated where David
Korn (the author of ksh) said "Oh, that's a bug, I didn't mean it to
Just for reference, the C standard says:
> If string is not a null pointer, the *system* function passes the string
pointed to
> by *string* to that command processor to be executed in a manner which
the implementation shall
> document; this might then cause the program calling system to behave in
The problem we were trying to address with this change is that bsd make
(bmake) and GNU make both have a := operator, but they behave differently.
We originally added ::= to match the gmake behavior. The idea with :::= is
to match the bmake behavior. There is then some further confusion because
"Resolved" means that the working group came to a consensus over how to
address the issue.
"Accepted as marked" means that we agreed to the problem, but we did not
resolve it as the original requester suggested ... there is alternate text
in the bugnote identified in "Final Accepted Text".
If the value is 200112L, then the implementation of the monotonic clock is
as specified in that version of the standard (where it was optional). If
the value is 200809L, then the implementation of the monotonic clock is as
specified in that version (where it was optional). And so on ...
The
ISO/IEC 9945:2009 including Corrigenda 1 (2013) and Corrigenda 2
(2017) is the current latest approved ISO standard. The Austin Group
is in the process of revising this, with a publication date in 2022
expected. You state "Since the TCs are just lists of changes, not a
complete document, ..."
