> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
TC> Ok, so you want message catalogues, and not solely on Perl but anything
TC> in the distribution. You should say that.
No. That is independent of what I'm suggesting. What I'm suggesting is
an enabler.
I've seen code that actually l
Ok, so you want message catalogues, and not solely on Perl but anything
in the distribution. You should say that.
--tom
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
TC> I'm saying that you can't know what to check for, because you don't
TC> know who generated the exception. Can you use your fancy constants?
Then please tell me how anyone has ever coded
$@ =~ //
They don't know what to
>> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
>>> Currently many programs handle error returns by examining the text of
>>> the error returned in $@. This makes changes in the text of the error
>>> message, an issue for the backwards compatibility police.
>TC> eval { fn() };
>
Perl6 RFC Librarian wrote:
[...]
> =head1 TITLE
>
> All perl generated errors should have a unique identifier
>
[...]
> An id string could have some structure associated to enable
> better handling. One suggestion was to follow the lead of VMS.
>
> facility:
> The program
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
>> Currently many programs handle error returns by examining the text of
>> the error returned in $@. This makes changes in the text of the error
>> message, an issue for the backwards compatibility police.
TC> eval { fn() };
TC>
>Currently many programs handle error returns by examining the text of
>the error returned in $@. This makes changes in the text of the error
>message, an issue for the backwards compatibility police.
eval { fn() };
if ($@ == EYOURWHATHURTS) { }
sub fn { die "blindlesnot" }
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
All perl generated errors should have a unique identifier
=head1 VERSION
Maintainer: Chaim Frenkel <[EMAIL PROTECTED]>
Date: 9 Aug 2000
Last Modified: 19 Sep 2000
Mailing List: [EMAIL PROTECTED]
N
