Re: indispensability of close()-checking [was: authorial perlipc edit]

2010-11-10 Thread Tom Christiansen
of "Thu, 11 Nov 2010 01: 08:02 +0100." References: <18061.1289240...@chthon> <20101109060255.9378.qm...@lists-nntp.develooper.com> <21672.1289313...@chthon> <29825.1289316...@chthon> <9570.1289357...@chthon> <25267.1289362...@chthon> <9217.1289400...@chthon> Mime-Version: 1.0 Cont

Re: indispensability of close()-checking [was: authorial perlipc edit]

2010-11-10 Thread Leon Timmermans
On Wed, Nov 10, 2010 at 3:53 PM, Tom Christiansen wrote: > However, streams are set up so that their error flag gets set on any > failed I/O operation, and this sticky flag carries through until the > ultimate close, whose return reflects that. I think PerlIO is currently not checking the ferror

indispensability of close()-checking [was: authorial perlipc edit]

2010-11-10 Thread Tom Christiansen
I wrote, quoting Leon: most of the time people don't check the return values of their print() calls, making the point of checking close() a bit moot IMHO. Also, closing a valid read-only filedescriptor can't even generate an error AFAIK. >>> Certainly it can!! >> Enlighten me