;fatal => { ... }
Agreed. That one is better than the different class :-)
--
Markus Peter - SPiN GmbH
[EMAIL PROTECTED]
for an exception which might be a problem but not very serious
and Error for the real, usually always fatal problems.
--
Markus Peter - SPiN GmbH
[EMAIL PROTECTED]
se who could still not see any sense in my words ;-):
use no fatal;
bla;
bla;
# should any of the above code throw an exception it gets ignored
try {
# from this point on i handle exceptions - use fatal is implied
foo;
} catch ...; # handle exception
bar;
...
bar;
# exceptions automatically ignored again
--
Markus Peter
[EMAIL PROTECTED]
nline RFC 88 - what version are we
talking about?
2) It's still fatal even if the program used 'no fatal' at the beginning
of the program, but outside the try block?
--
Markus Peter
[EMAIL PROTECTED]
use fatal/no fatal would not allow this I think
as suddenly those modules could stop throwing exceptions, so I'd end up
enable/disabling use fatal all the time...
Another way to achieve the same result would be to NOT get rid of the try
part of try/catch and then try automatically implies use fatal for that
block...
--
Markus Peter
[EMAIL PROTECTED]
without the need to span a try/catch block across my whole
main program - I simply do not like the look and feel of that. Even though
this has global effects, it's not necessarily evil, we should only ensure
that it cannot be used from within a .pm
--
Markus Peter - SPiN GmbH
[EMAIL PROTECTED]
error
modes), so that I can check exceptions when I want to
--
Markus Peter - SPiN GmbH
[EMAIL PROTECTED]
