One of design philosophies of OIO was to use an
object-oriented approach to error handling as suggested in
Damian Conway's book "Perl Best Practices." By using
Exception::Class for this, OIO is meant to work with custom
exception handling.
The need for "local $SIG{'__DIE__'};" statements inside
:Init, etc. subroutines is documented in the POD, but not
specifically for purpose you outlined. I'll try to expand
on this for the next release. Thanks.
In your example, aside from adding "local $SIG{'__DIE__'};"
to the 'eval' in _init(), if you create your own
Exception::Class objects, you can generate the type of
behavior I think you're looking for:
(2)
]
