Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Ariel Scolnicov
Perl6 RFC Librarian [EMAIL PROTECTED] writes, for Chaim Frenkel [EMAIL PROTECTED]: [...] =item As a floating point number The integer part would be the actual identifier. The fractional part could encode some classification scheme. Floating point numbers don't work this way. Suppose I

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Uri Guttman
"AS" == Ariel Scolnicov [EMAIL PROTECTED] writes: AS 2. Error codes as digit strings with decimal point. So "123.4567" AS(_not_ 123.4567) represents error 4567. People will still try ASstupid floating-point math tricks to get at the suberror code, but ASat least we'll know

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Chaim Frenkel
I'm leaning to splitting identifier from the classification. A pure monotonically increasing integer would ensure the non-reuse. And the classification scheme could evolve seperately. Using numbers for the classification scheme would require a translation table. So why not just use

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Peter Scott
At 10:42 PM 8/10/00 -0400, Chaim Frenkel wrote: PS 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

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Nathan Wiger
well, if it is only a string, why use . as the separator? use something else like : and no one will try any fancy math tricks on it. Agreed. I like :, it's a common separator. Also, how about just $@-id? Shorter and I would argue the "unique_" is really redundant (id's are usually unique,

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Juanma Barranquero
On 10 Aug 2000 22:26:47 -, Chaim Frenkel [EMAIL PROTECTED] wrote: =head2 Encodings I have listed some possiblities. But none of these are ideal. =head3 A unique number =item As an integer =item As a floating point number =head3 Unique String =head3 Prefixes for all error strings

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Chaim Frenkel
"NW" == Nathan Wiger [EMAIL PROTECTED] writes: NW Also, how about just $@-id? Shorter and I would argue the "unique_" is NW really redundant (id's are usually unique, hence the name NW "identifiers"). Not really. Consider: Chaim is an identifier. But not unique. chaim -- Chaim Frenkel

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Nathan Wiger
Chaim Frenkel wrote: "NW" == Nathan Wiger [EMAIL PROTECTED] writes: NW Also, how about just $@-id? Shorter and I would argue the "unique_" is NW really redundant (id's are usually unique, hence the name NW "identifiers"). Not really. Consider: Chaim is an identifier. But not

RFC 85 (v1) All perl generated errors should have a

2000-08-10 Thread Perl6 RFC Librarian
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 Version: 1 Mailing List: [EMAIL PROTECTED] Number: 85 All

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-10 Thread Tony Olekshy
Chaim Frenkel wrote: [stuff about exception numbering] 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. RFC 88 goes to some trouble to seperate exception handling from exception objects. It