Mercurial > hg > octave-kai > gnulib-hg
view doc/posix-functions/signal.texi @ 17085:80904f782122
doc: document sticky-EOF issue
* doc/posix-functions/fgetc.texi (fgetc):
* doc/posix-functions/fgets.texi (fgets):
* doc/posix-functions/fread.texi (fread):
* doc/posix-functions/fscanf.texi (fscanf):
* doc/posix-functions/getc.texi (getc):
* doc/posix-functions/getchar.texi (getchar):
* doc/posix-functions/scanf.texi (scanf):
Mention that glibc and default Solaris do not conform to
C99 and POSIX-2001 or later, with respect to how getchar
etc. behave when feof reports nonzero.
author | Paul Eggert <eggert@cs.ucla.edu> |
---|---|
date | Sun, 16 Sep 2012 10:37:16 -0700 |
parents | a27be0e3ac06 |
children |
line wrap: on
line source
@node signal @section @code{signal} @findex signal POSIX specification:@* @url{http://www.opengroup.org/onlinepubs/9699919799/functions/signal.html} Gnulib module: --- Portability problems fixed by Gnulib: @itemize @end itemize Portability problems not fixed by Gnulib: @itemize @item This function crashes when invoked with invalid arguments on some platforms: MSVC 9. @item On System V platforms, when the signal is triggered, the kernel uninstalls the handler (i.e.@: resets the signal's action to SIG_DFL) before invoking the handler. This opens the door to race conditions: undesired things happen if the signal is triggered twice and the signal handler was not quick enough reinstalling itself as a handler. On BSD platforms and glibc platforms, on the other hand, when the signal is triggered, the kernel blocks the signal before invoking the handler. This is saner, but POSIX still allows either behavior. To avoid this problem, use @code{sigaction} instead of @code{signal}. @end itemize