| 17,20 → 17,31 |
|---|
| |
| /* |
| FUNCTION |
| <<ferror>>---test whether read/write error has occurred |
| <<ferror>>, <<ferror_unlocked>>---test whether read/write error has occurred |
| |
| INDEX |
| ferror |
| INDEX |
| ferror_unlocked |
| |
| ANSI_SYNOPSIS |
| #include <stdio.h> |
| int ferror(FILE *<[fp]>); |
| |
| #define _BSD_SOURCE |
| #include <stdio.h> |
| int ferror_unlocked(FILE *<[fp]>); |
| |
| TRAD_SYNOPSIS |
| #include <stdio.h> |
| int ferror(<[fp]>) |
| FILE *<[fp]>; |
| |
| #define _BSD_SOURCE |
| #include <stdio.h> |
| int ferror_unlocked(<[fp]>) |
| FILE *<[fp]>; |
| |
| DESCRIPTION |
| The <<stdio>> functions maintain an error indicator with each file |
| pointer <[fp]>, to record whether any read or write errors have |
| 39,6 → 50,15 |
|---|
| |
| See <<clearerr>> to reset the error indicator. |
| |
| <<ferror_unlocked>> is a non-thread-safe version of <<ferror>>. |
| <<ferror_unlocked>> may only safely be used within a scope |
| protected by flockfile() (or ftrylockfile()) and funlockfile(). This |
| function may safely be used in a multi-threaded program if and only |
| if they are called while the invoking thread owns the (FILE *) |
| object, as is the case after a successful call to the flockfile() or |
| ftrylockfile() functions. If threads are disabled, then |
| <<ferror_unlocked>> is equivalent to <<ferror>>. |
| |
| RETURNS |
| <<ferror>> returns <<0>> if no errors have occurred; it returns a |
| nonzero value otherwise. |
| 46,6 → 66,8 |
|---|
| PORTABILITY |
| ANSI C requires <<ferror>>. |
| |
| <<ferror_unlocked>> is a BSD extension also provided by GNU libc. |
| |
| No supporting OS subroutines are required. |
| */ |
| |