Re: Returning 0 vs throwing errors in Stdio

The benefits are there in the CVS message

revision 1.204 date: 2004/09/01 17:17:08; author: mast; state: Exp; lines: +78 -30 Made read_file, read_bytes, write_file and append_file easier to use by letting them throw on all I/O errors (with the exception that read_file and read_bytes still returns zero if the file doesn't exist at all). For instance, it's not necessary to check the return value from write_file and append_file to ensure that the whole string was written. ----------------------------

and I agree with them. I don't think this breaks much code, if any, only makes the flaws in that code more visible, should it occur. I know that I never check errno after performing Pike file I/O.