At 03:27 PM 2/13/01 +0000, Nicholas Clark wrote:
>I fear I'm not adding anything apart from noise to this debate.
>(partly from not having thought through the issues completely, partly by
>not reading the full archives for the list from last year)
>
>On Mon, Feb 12, 2001 at 01:58:35PM -0700, Tony Olekshy wrote:
> > Or as Larry said in his ALS talk, "a completely object-oriented
> > exception handling, with a simple string-like interface for those
> > who do not want the power of the full OO system." See the notes
> > at http://www.avrasoft.com/perl6/rfc88.htm#CONVERSION for more
> > information on how this works.
>
> my $f = open $file or die "can't open $file";
>
>is troublesome. It doesn't report *why* the file can't be opened.
>
>[snip]
>errno is not flexible. *flexible* exceptions are needed
>[snip]
>I think that it would be nice in 5.8 to (optionally on some pragma?) make
>print, close and a few others in void context croak.
>
>It would actually make writing perl scripts easier. You'd know when your
>disk became full (or you went over quota), albeit in with a messy error.
>OK, script crashing with an uncaught exception isn't nice, but it's nicer
>than silently losing data IMHO.
I think you'll find this addressed already in RFCs 70, 80, and 151. At
least, that was my intention.
http://dev.perl.org/rfc/70.html
http://dev.perl.org/rfc/80.html
http://dev.perl.org/rfc/151.html
--
Peter Scott
Pacific Systems Design Technologies
