At 12:16 PM 8/27/00 -0400, Bennett Todd wrote:
> > The ramifications of some of these things are sufficiently
> > important that drawing attention to them might be a good thing.
> > In this case, note that Perl 6 will need to spell out which core
> > exceptions are by default fatal (eg, :arithmetic) and which
> > aren't. Although RFC 70 doesn't have to do that.
>
>It feels to me like this should maybe be divided into some change to
>RFC 70, along with a companion RFC --- unless you want to fold all
>discussion of Fatal.pm development into 70. But if you like I'll be
>happy to include in RFC 70 the request that any builtins that
>_by_default_ "throw exceptions" (die) on errors, _also_ be wrappable
>so that Fatal.pm can be written to allow e.g. "no Fatal
>qw(:arithmetic)". Of course that specific one may require additional
>intimacy between Fatal and the core, since unless we make all
>arithmetic scalars into objects, I don't think we're set up to allow
>overriding basic arithmetic builtins like e.g. "/" for
>divide-by-zero.
I don't think you need to get into the -internals part of it. Although if
you were, I'd say that where pp.c does
DIE(aTHX_ "Illegal division by zero");
the DIE will be turned into something that checks fatalism first.
--
Peter Scott
Pacific Systems Design Technologies
