Hi,
>>"Steve" == Steve Greenland <[EMAIL PROTECTED]> writes:
Steve> On 11-Apr-98, 02:26 (CDT), Manoj Srivastava
Steve> <[EMAIL PROTECTED]> wrote:
>> So, the point is not whether they implemntation can do strange and
>> unexpected things; they can; but then they have to document it.
>>
>> BTW, in Debian, fclose says it returns an error, and does not
>> mention corrupting memory. ERRORS EBADF The argument stream is not
>> an open stream.
>>
>> The fclose function may also fail and set errno for any of the
>> errors specified for the routines close(2) or fflush(3).
Steve> Oh, sure, that's an error it *may* report, *if* it detects
Steve> it. I don't see anything on the man page that would expect me
Steve> to believe that the implementation will detect all possible
Steve> invalid streams and report an error. I am also quite willing to
Steve> believe that the particular error we are discussing
Steve> (fclose(fp);fclose(fp)) will be detected.
Fair enough. In which case this should be documented.
Steve> Unfortunately, that belief is not supported.
Then this is a defect in the implementation.
manoj
--
There are two ways to improve on human factors in computing: Make the
programmers less stupid and/or make the users less stupid. Both are
necessary, neither are likely. Digital Teddy Bear
([EMAIL PROTECTED])
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
