[PATCH v5 4/8] Cygwin: winsup/doc/posix.xml: SUS V5 POSIX 2024 move or remove dropped entries

[Corinna Vinschen]

On Jan 12 13:00, Brian Inglis wrote:
> On 2025-01-12 11:04, Jon Turney wrote:
> > On 11/01/2025 00:01, Brian Inglis wrote:
> > > Move entries no longer in POSIX from the SUS/POSIX section to
> > > Deprecated Interfaces section and mark with (SUSv4).
> > > Remove entries no longer in POSIX from the NOT Implemented section.
> > > 
> > [...]
> > > -<sect1 id="std-deprec"><title>Other UNIX system interfaces, not in
> > > POSIX.1-2008 or deprecated:</title>
> > > +<sect1 id="std-deprec"><title>Other UNIX® system interfaces, not in
> > > POSIX.1-2024, or deprecated:</title>
> > 
> > Maybe we've reached the point where this could be split into "System
> > interfaces deprecated in POSIX.1-2024" and "Other UNIX system
> > interfaces, not in POSIX.1-2024"?
> 
> Or just drop "deprecated" as these interfaces have been dropped from POSIX
> 2024, which is why I moved getdomainname to Solaris/SunOS and added "(NIS)"!

You both have a point.  There are two or more problems with the section.
For instance, it contains entries like bcmp, bcopy, bzero, which, yes,
have been deprecated from POSIX, but are actually 4.3BSD functions.
So those would have to be moved to the std-bsd section.

Just as gethostbyaddr, gethostbyname, ftime, etc.

cuserid was System V.

ecvt/fcvt/gcvt are old as dirt, probably System 7.

on_exit is SunOS, so why the heck did I add it to the std-deprec
section 10 years ago?

ETC

So, is there really any of them, which have been first added as part of
the POSIX standard and then have been deprecated again, or were all of
them part of an older or different OS?  If so, the expression
"deprecated" wouldn't make much sense, and the section would only
contain a few SVID functions and the really exotic stuff like

  clock_setres                (QNX, VxWorks)
  pthread_getsequence_np      (Tru64)
  gethostbyname2              (first defined in BIND 4.9.4)


Corinna