Re: cvs: php4 /ext/standard file.c

At 06:22 PM 12/22/00 +0100, Sascha Schumann wrote:

It can't hurt to use a full_write()/full_read() in most places. Worst case it doesn't help.

    No, the worst case is that our process gets terminated.

Uhm, I obviously meant that if the process doesn't get terminated. Not on all systems do you get a signal if the disk is full. On Linux as far as I remember, write() returns an error code. Not that this has anything to do with what I said in the first place. On systems which send you a signal you'll also get a signal in both cases. Anyway, if you feel comfortable with the way it is than leave it for now. When I have time I'll add full_write() and full_read() API functions so that they can be used by extension writers. Let's not drag out this thread. It's pretty common knowledge that full_write()/full_read() are very useful to most ppl who don't want to start testing read()/write(). And I am pretty sure (although I haven't checked) that most PHP coders haven't handled this correctly. Andi --- Andi Gutmans <andi@zend.com> http://www.zend.com/