>> If you do it the C++ way, you can say:
>>   try {
>>     first_sub_that_throws_exceptions();
>>     second_sub_that_throws_exceptions();
>>   } catch {
>>     it went wrong 
>>   }

>How does 'it went wrong' know _which_ of the subs went wrong? 
    ....

This is my argument against obsolescing the general-purpose socket() et al.
syscalls in deference to the IO::Socket stuff:  You don't know what blew
up, and lack fine-grained control.  (There's also the matter of being 
somewhat non-useful for UDP.)

--tom

Reply via email to