On Wed, May 09, 2001 at 08:42:40AM -0600, Sterin, Ilya wrote:
> Now as I read it a few times, I can make sense out of it. Just a long day
> yersterday. Although it can be a little bit more clearly explained for
> challenged people like myself:-)
>
> I guess maybe reverse thinking...
>
> ***
> If `PrintError' is also on, then it will be skipped
> since the 'die' will print the message, unless '__DIE__' handler
> is defined in which case 'PrintError' is done before 'RaiseError'.
> ***
>
> Sounds like the same thing, but when reading for the first time can make
> more sense, since in most cases '__DIE__' is probably not defined, so that
> condition is more commone and should come first. Anyone??
Umm, first I changed it to say:
: If you turn C<RaiseError> on then you'd normally turn C<PrintError> off.
: If C<PrintError> is also on, then the C<PrintError> is skipped if the DBI
: thinks the exception about to be trigged by C<RaiseError> will not be
: caught. (Currently the DBI only considers a C<$SIG{__DIE__}> hook
: and catching an exception. That'll be fixed one day to include eval.)
but now I've changed it to say:
: If you turn C<RaiseError> on then you'd normally turn C<PrintError> off.
: If C<PrintError> is also on, then the C<PrintError> is done first (naturally).
In other words, I've removed the trying-to-be-too-clever logic.
If you ask for both PrintError and RaiseError then that's what you get.
:)
Tim.