Hi Brian, On Jan 10 17:01, Brian Inglis wrote: > Update anchor id and description to current version, year, issue, etc. > Move new POSIX entries in other sections to the SUS/POSIX section. > > Signed-off-by: Brian Inglis <brian.ing...@systematicsw.ab.ca> > --- > winsup/doc/posix.xml | 140 ++++++++++++++++++++++--------------------- > 1 file changed, 73 insertions(+), 67 deletions(-) > > diff --git a/winsup/doc/posix.xml b/winsup/doc/posix.xml > index 2782beb86547..1b893e9e19ae 100644 > --- a/winsup/doc/posix.xml > +++ b/winsup/doc/posix.xml > @@ -5,10 +5,16 @@ > <chapter id="compatibility" xmlns:xi="http://www.w3.org/2001/XInclude";> > <title>Compatibility</title> > > -<sect1 id="std-susv4"><title>System interfaces compatible with the Single > Unix Specification, Version 7:</title> > +<sect1 id="std-susv5"><title>System interfaces compatible with the Single > UNIX® Specification Version 5:</title> > > -<para>Note that the core of the Single Unix Specification, Version 7 is > -also IEEE Std 1003.1-2017 (POSIX.1-2017).</para> > +<para>Note that the core of the Single UNIX® Specification Version 5 is > +POSIX®.1-2024 also simultaneously IEEE Std 1003.1™-2024 Edition, > +The Open Group Base Specifications Issue 8 > +(see https://pubs.opengroup.org/onlinepubs/9799919799/), and > +ISO/IEC DIS 9945 Information technology > +- Portable Operating System Interface (POSIX®) base specifications > +- Issue 8 (expected to replace ISO/IEC/IEEE 9945:2009 - Issue 7 in the > coming months
This hint is outdating itself. It might be a good idea to phrase it time-independent... > <sect1 id="std-iso"><title>System interfaces not in POSIX but compatible > with ISO C requirements:</title> > > <screen> > - aligned_alloc (ISO C11) > - at_quick_exit (ISO C11) > - c16rtomb (ISO C11) > - c32rtomb (ISO C11) > c8rtomb (ISO C23) Did they really miss to standarize c8rtomb/mbrtoc8 as well? I guess C23 was too fresh... ;) Corinna
