On Sun, 16 Feb 2025 at 22:47, Mark Geisert <m...@maxrnd.com> wrote: > > In the doc tree, change the title of section "Other UNIX system > interfaces..." to "Other system interfaces...". Add the spawn family of > functions noting their origin as Windows.
re spawn() family: Cygwin posix_spawn() seems to rely on the rather inefficient vfork(), while Opengroup intended it to be an API to Windows spawn(). Is there a technical limitation why Cygwin posix_spawn() cannot use WinAPI spawn() directly? Lionel > > The title change seems warranted as neither the spawn family of > functions nor the listed clock_setres() function originated from UNIX > systems. > > --- > winsup/doc/posix.xml | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/winsup/doc/posix.xml b/winsup/doc/posix.xml > index 26d4fcfa4..3d2dac086 100644 > --- a/winsup/doc/posix.xml > +++ b/winsup/doc/posix.xml > @@ -1559,7 +1559,7 @@ also IEEE Std 1003.1-2017 (POSIX.1-2017).</para> > > </sect1> > > -<sect1 id="std-deprec"><title>Other UNIX system interfaces, not in > POSIX.1-2008 or deprecated:</title> > +<sect1 id="std-deprec"><title>Other system interfaces, not in POSIX.1-2008 > or deprecated:</title> > > <screen> > bcmp (POSIX.1-2001, SUSv3) > @@ -1568,6 +1568,7 @@ also IEEE Std 1003.1-2017 (POSIX.1-2017).</para> > chroot (SUSv2) (see <xref > linkend="std-notes">chapter "Implementation Notes"</xref>) > clock_setres (QNX, VxWorks) (see <xref > linkend="std-notes">chapter "Implementation Notes"</xref>) > cuserid (POSIX.1-1988, SUSv2) > + cwait (Windows) > ecvt (SUSv3) > endutent (XPG2) > fcvt (SUSv3) > @@ -1602,6 +1603,14 @@ also IEEE Std 1003.1-2017 (POSIX.1-2017).</para> > scalb (SUSv3) > setcontext (SUSv3) > setutent (XPG2) > + spawnl (Windows) > + spawnle (Windows) > + spawnlp (Windows) > + spawnlpe (Windows) > + spawnv (Windows) > + spawnve (Windows) > + spawnvp (Windows) > + spawnvpe (Windows) > stime (SVID) > swapcontext (SUSv3) > sys_errlist (BSD) > -- > 2.45.1 > -- Lionel -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
