>>>>> "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
>> =head1 TITLE
>>
>> All perl generated errors should have a unique identifier
PS> This looks awfully similar to RFC 80. Certainly the exception objects RFC
PS> 80 is thinking about can well have unique numeric attributes.
>> All perl generated errors should have a unique identity. So that
>> changes in the text should not cause breakage in code.
PS> Amen. Can this be merged with RFC 80, or do they need to live apart?
I believe they do. This portion can independently survive without
an exception mechanism. I'm only addressing the "what error did
I get". You are addressing the error handling mechanism.
Also, my RFC could be useful for those who are adamant or reluctant
to put a full fledged exception mechanism in. All they want is the
value $@ (or perhaps the error identifier).
Perhaps, RFC 80 could reference this document? I'll put in suggested
hierarchies (though that might be considered an implementation detail.
Since we cannot know in advance how the errors would be distributed.)
>> FIL0001W unable to close filehandle %s properly
>> PAR0003F Can't find label %s
PS> Or %VMS-F-ACCVIO, access violation :-)
I really would like some suggestions on how to structure the identifier.
So far, I have the IBM and VMS styles.
>> =head2 Classification Schemes
>>
>> To be defined. Suggestions welcome.
PS> I made a start in RFC 80.
Have you looked at the current scheme used by lexical warnings?
Hmm, I thought I saw another exception RFC pass by. ..... Yup,
RFC 88, Tony Olekshy <[EMAIL PROTECTED]>
Could you two folks get together and hash this out.
(I think Graham's nomenclature would be more perlish....)
<chaim>
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
