RE: RFC 80 (v4) Exception objects and classes for builtins

On Wednesday, October 04, 2000 1:21 AM, Perl6 RFC Librarian 
[SMTP:[email protected]] wrote:
> This and other RFCs are available on the web at
>   http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Exception objects and classes for builtins
>
> =head1 VERSION
>
>   Maintainer: Peter Scott <[email protected]>
>   Date: 9 Aug 2000
>   Last Modified: 3 Oct 2000
>   Mailing List: [email protected]
>   Number: 80
>   Version: 4
>   Status: Frozen
>
> =head1 ABSTRACT
>
> This RFC proposes that builtins that throw exceptions throw them as objects
> belonging to a set of standard classes.  This would enable an exception
> type to be easily recognized by user code.  The behavior if the exception
> were not trapped should be identical to the current behavior (error message
> with optional line number output to STDERR and exit with non-zero exit code).
>
> =head1 DESCRIPTION
>
> This RFC is tightly bound with RFC 88, which proposes an exception handling
> mechanism based upon exceptions-as-objects, and in particular specifies
> that fatal exceptions thrown by the core will be objects with certain
> instance attributes.  We assume here that these aspects of RFC 88 are
> implemented.
>
> Builtins experiencing fatal errors currently call C<die>, which is to say,
> they throw an exception.  Builtins experiencing non-fatal errors return a

I'm sorry. I would still consider this a sick perversion of the language and a 
violation of its purposeful simplicity unless this was completely optional and 
hidden (i.e., not default). I know some people are hog wild about exceptions 
nowadays, but ||die is still perlish and my WTDI.