[EMAIL PROTECTED] (Larry Jones) writes: > Aaron Stone writes: >> >> If I were using a function like this, I'd expect NULL on error (and >> errno set according to fopen), and an empty string if the file is empty. > > Note that the C Standard doesn't require fopen to set errno and > traditional implementations didn't, at least in some cases.
The docstring intentionally avoids saying that errno is set to something useful: *LENGTH. On errors, *LENGTH is undefined, errno preserves the values set by system functions (if any), and NULL is returned. */ I guess it could explicitly set errno, but I'm not sure that is such a good style either...
