[PATCH v3] Cygwin: Add spawn family of functions to docs
In the doc tree, add a new section "Other system interfaces[...]" that lists the spawn family of functions, most of the exposed cygwin internal functions that a user might have use for, and some other functions duplicating Windows or DOS interfaces that might have some utility. --- winsup/doc/posix.xml | 32 1 file changed, 32 insertions(+) diff --git a/winsup/doc/posix.xml b/winsup/doc/posix.xml index 43e860b0d..748f243f6 100644 --- a/winsup/doc/posix.xml +++ b/winsup/doc/posix.xml @@ -1762,6 +1762,38 @@ ISO®/IEC DIS 9945 Information technology +Other system interfaces, some from Windows: + + +_get_osfhandle (Windows) +_setmode (Windows) +cwait (Windows) +cygwin_attach_handle_to_fd +cygwin_conv_path +cygwin_conv_path_list +cygwin_create_path +cygwin_detach_dll +cygwin_dll_init +cygwin_internal +cygwin_logon_user +cygwin_posix_path_list_p +cygwin_set_impersonation_token +cygwin_split_path +cygwin_stackdump +cygwin_umount +cygwin_winpid_to_pid +spawnl (Windows) +spawnle(Windows) +spawnlp(Windows) +spawnlpe (Windows) +spawnv (Windows) +spawnve(Windows) +spawnvp(Windows) +spawnvpe (Windows) + + + + Implementation Notes chroot only emulates a chroot function call -- 2.45.1
Re: [PATCH v2] Cygwin: Add spawn family of functions to docs
Hi Mark, a few points: On Feb 25 22:37, Mark Geisert wrote: > In the doc tree, add a new section "Other system interfaces[...]" that > lists the spawn family of functions, most of the exposed cygwin internal > functions that a user might have use for, and some other functions > duplicating Windows or DOS interfaces that might have some utility. > > --- > winsup/doc/posix.xml | 35 +++ > 1 file changed, 35 insertions(+) > > diff --git a/winsup/doc/posix.xml b/winsup/doc/posix.xml > index 43e860b0d..b9443eaae 100644 > --- a/winsup/doc/posix.xml > +++ b/winsup/doc/posix.xml > @@ -1762,6 +1762,41 @@ ISO®/IEC DIS 9945 Information technology > > > > +Other system interfaces, some from > Windows: > + > + > +_alloca (Windows) Uhm... yeah, we export this symbol. Because it's (incorrectly) used by some apps like cmake. They should use alloca which translates to __builtin_alloca in GCC, but... well... OTOH, do we really WANT to expose this via our docs? I think no. > +_feinitialise _feinitialise is internal only and called from the DLL init code. We export this symbol only for old applications, see Cygwin's fenv.c. > +_get_osfhandle (Windows) > +_pipe(Windows) We export _pipe, but I don't remember why, and it's not in any header. We shouldn't document it. Looks good, otherwise. Thanks, Corinna
