> "JM" == James Mastros <[EMAIL PROTECTED]> writes:
JM> On Mon, Aug 14, 2000 at 06:17:02PM -0400, Chaim Frenkel wrote:
>> Let us get away from the globals as much as we can. This can easily
>> (I think) be taken care of by having the _exception_ itself have the
>> uncaught handler
>>
>> $exc
On Mon, Aug 14, 2000 at 06:17:02PM -0400, Chaim Frenkel wrote:
> Let us get away from the globals as much as we can. This can easily
> (I think) be taken care of by having the _exception_ itself have the
> uncaught handler
>
> $exception = Exception::whatever->new
> $exception->uncaug
James Mastros wrote:
> My proposal is:
> $Exceptiononuncaught = CODEREF.
>
> The value of onuncaught should follow isa if it doesn't exist.
>
This would be right at home in the pre-RFC %ISA hash of
objecty stuff $ISA{ONUNCAUGHT} instead of a global. Creating
$whatever::ISA{O
Let us get away from the globals as much as we can. This can easily
(I think) be taken care of by having the _exception_ itself have the
uncaught handler
$exception = Exception::whatever->new
$exception->uncaught_handler = CODEREF
> "JM" == James Mastros <[EMAIL PROTECTED]>
From: "Peter Scott" <[EMAIL PROTECTED]>
Sent: Sunday, August 13, 2000 10:35 PM
> try {
># fragile code which doesn't call any subroutines that might die
># and doesn't include any other try blocks
> } catch {
># No code at all
> }
Well, I don't really like that solution. It's exactly
At 03:30 PM 8/13/00 -0500, David L. Nicol wrote:
>Whose RFC deals with this?
63, 70, 80, 88 and 96. There would appear to be a groundswell of interest :-)
The mailing list for discussing this is [EMAIL PROTECTED]
>Further discussion in the thread discussed the idea of returning
>to the point
