>> 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
- Re: RFC: Modify open() and opendir() to return handles Tom Christiansen
- Re: RFC: Modify open() and opendir() to return handles Graham Barr
- Re: RFC: Modify open() and opendir() to return handles Tim Jenness
- Re: RFC: Modify open() and opendir() to return handles Peter Scott
- Re: RFC: Modify open() and opendir() to return handles Johan Vromans
- Re: RFC: Modify open() and opendir() to return handles Steve Simmons
- try/catch (Was: Re: RFC: Modify open() and opendir() t... Johan Vromans
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Hildo Biersma
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Johan Vromans
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Graham Barr
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Tom Christiansen
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Graham Barr
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Nathan Wiger
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Tom Christiansen
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Nathan Wiger
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Tom Christiansen
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Nathan Torkington
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Tom Christiansen
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Peter Scott
- Re: try/catch (Was: Re: RFC: Modify open() and opendir... Steve Simmons
- Re: RFC: Modify open() and opendir() to return handles Jonathan Scott Duff
