Re: Writing to the hard disk, and checking for error to exit(1)?
- From: "Harald van Dijk" <truedfx@xxxxxxxxx>
- Date: 13 Dec 2006 11:56:43 -0800
matevzb wrote:
On Dec 13, 7:33 pm, Richard Heathfield <r...@xxxxxxxxxxxxxxx> wrote:
<snip>
Look up ferror(). Cf <stdio.h>
Also consider using EXIT_FAILURE instead of 1. Cf <stdlib.h>
There was (still is?) an issue with HPUX where fprintf() would block if
the disk got full, so this might not always work. Does this behaviour
conform to the Standard? I only found "The fprintf function returns the
number of characters transmitted, or a negative value if an output or
encoding error occurred."
It can conform to the standard. But then again, an implementation that
waits three days after each statement can also conform to the standard.
.
- References:
- Writing to the hard disk, and checking for error to exit(1)?
- From: eastcoastguyz
- Re: Writing to the hard disk, and checking for error to exit(1)?
- From: Richard Heathfield
- Re: Writing to the hard disk, and checking for error to exit(1)?
- From: matevzb
- Writing to the hard disk, and checking for error to exit(1)?
- Prev by Date: Re: File Size Limit Exceeded - How to handle work around this?
- Next by Date: Re: memcpy and volatile
- Previous by thread: Re: Writing to the hard disk, and checking for error to exit(1)?
- Next by thread: Re: Writing to the hard disk, and checking for error to exit(1)?
- Index(es):
Relevant Pages
|
