Re: RFC 78 (v1) Improved Module Versioning And Searching

[Dan Sugalski]

At 05:46 PM 8/10/00 +0100, Graham Barr wrote:
>On Thu, Aug 10, 2000 at 12:28:05PM -0400, Dan Sugalski wrote:
> > No, it wouldn't, really. We could make "use fatal;" scoped, so that the
> > quit op (or whatever it is) only jumps through all its hoops if the
> > pragma's in effect. If its not, then quit(foo, bar, baz) does a bare 
> return
> > and that's it.
> >
> > You'd have the overhead of checking a flag when actually quitting with an
> > error, but that adds a very small amount of overhead to an exceptional 
> case.
>
>Why not make that flag avaliable instead of having a new op ?
>
>The user can then write
>
>   $^fatal ? die .... : return;

Sure, that works. Whatever keyword throws the non-fatal error might just be 
a perl sub that does exactly that, at least to start. (Maybe always, who knows)

>Hm, although people may start to mis-use the flag.

What, people misuse core functionality? I can't picture *that* happening. 
It's so unperlish... :)

                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk