On 8 Sep 2000, Chaim Frenkel wrote:
> >> Oh, why not? Does anybody actually *ever* check the return value of
> >> print? I think it's not as if we'd break a lot of code.
>
> ABH> uh, what? you don't do much socket programming now, do you? sockets
> ABH> breaks all the time. Disks runs out of space while you write to
> ABH> files. and so on and so on.
>
> Could someone enlighten this poor soul and tell me what I _can_ do
> with an error return from a print or close?
rollback transactions to the database, flag the thing you tried to
do as something that should be retried, close and reopen the socket
connection and try again, send a mail to the NOC that the world is
on fire, etcetera, etcetera ...
Tim always refers to
http://search.cpan.org/doc/TIMB/DBI_Talk4_2000/sld024.htm
> Reporting it may be useless (disk full).
eh? I like to get someone aware of it so the problem can be fixed. I
also like my application to stop doing whatever it tried to do and
if possibly know what it didn't do so it can try it again later.
- ask
--
ask bjoern hansen - <http://www.netcetera.dk/~ask/>
more than 70M impressions per day, <http://valueclick.com>
