Re: Draft 3 of RFC 88 version 2.

2000-08-23 Thread Peter Scott
At 04:38 PM 8/22/00 -0600, Tony Olekshy wrote: >Peter Scott wrote: > > > > I thought the discussion was around how > > > > throw object; > > > > could be a run-time error if object ! isa Exception (which is > > what I think should happen) if > > > > throw LIST; > > > > had to hav

Re: Draft 3 of RFC 88 version 2.

2000-08-22 Thread Tony Olekshy
Peter Scott wrote: > > I thought the discussion was around how > > throw object; > > could be a run-time error if object ! isa Exception (which is > what I think should happen) if > > throw LIST; > > had to have the same semantics as die LIST. We can't do constuctor and LIS

Re: Draft 3 of RFC 88 version 2.

2000-08-22 Thread David L. Nicol
> Does this cover all the cases? > Does it allow not only die but everything w/in Carp.pm to be implemented in terms of it? -- David Nicol 816.235.1187 [EMAIL PROTECTED] Laziness with responsibility http://www.tipjar.com/kcpm

Re: Draft 3 of RFC 88 version 2.

2000-08-22 Thread Peter Scott
At 12:43 AM 8/20/00 -0600, Tony Olekshy wrote: >Peter Scott wrote: > > > > At 08:43 PM 8/19/00 -0600, Tony Olekshy wrote: > > >Peter Scott wrote: > > > > > > > > Dave Rolsky wrote: > > > > > > > > > > Tony Olekshy wrote: > > > > > > > > > > > > die > > > > > > If argument is anything else, ra

Re: Draft 3 of RFC 88 version 2.

2000-08-21 Thread Chaim Frenkel
> "TO" == Tony Olekshy <[EMAIL PROTECTED]> writes: TO> Perl's behaviour after a C starts call-stack unwinding, as TO> envisioned by this RFC, is as described by the following rules. TO> 1. Whenever an exception is raised Perl looks for an enclosing TO> try/catch/finally clause. TO>

Re: Draft 3 of RFC 88 version 2.

2000-08-19 Thread Tony Olekshy
Peter Scott wrote: > > At 08:43 PM 8/19/00 -0600, Tony Olekshy wrote: > >Peter Scott wrote: > > > > > > Dave Rolsky wrote: > > > > > > > > Tony Olekshy wrote: > > > > > > > > > > die > > > > > If argument is anything else, raise a run-time > > > > > exception. > > > > > > > > So this pro

Re: Draft 3 of RFC 88 version 2.

2000-08-19 Thread Peter Scott
At 08:43 PM 8/19/00 -0600, Tony Olekshy wrote: >Peter Scott wrote: > > > > Dave Rolsky wrote: > > > > > > Tony Olekshy wrote: > > > > > > > > die > > > > If argument is anything else, raise a run-time > > > > exception. > > > > > > So this probably shouldn't be the case. > > > > This soun

Re: Draft 3 of RFC 88 version 2.

2000-08-19 Thread Tony Olekshy
Peter Scott wrote: > > Dave Rolsky wrote: > > > > Tony Olekshy wrote: > > > > > > die > > > > > > If argument isa "Exception", raise it as the new > > > exception and die in the fashion that Perl 5 does. > > > > > > If argument is a string, wrap it in a new Error > > > object, set

Re: Draft 3 of RFC 88 version 2.

2000-08-19 Thread Peter Scott
At 09:22 PM 8/19/00 -0500, Dave Rolsky wrote: >On Sat, 19 Aug 2000, Tony Olekshy wrote: > > > die > > > > If argument isa "Exception", raise it as the new exception and > > die in the fashion that Perl 5 does. > > > > If argument is a string, wrap it in a new Error object, setting > >

Re: Draft 3 of RFC 88 version 2.

2000-08-19 Thread Dave Rolsky
On Sat, 19 Aug 2000, Tony Olekshy wrote: > die > > If argument isa "Exception", raise it as the new exception and > die in the fashion that Perl 5 does. > > If argument is a string, wrap it in a new Error object, setting > the message ivar to the given string, and raise that in

Draft 3 of RFC 88 version 2.

2000-08-19 Thread Tony Olekshy
=head1 TITLE Structured Exception/Error Handling Mechanism =head1 VERSION Maintainer: Tony Olekshy <[EMAIL PROTECTED]> Date: 19 Aug 2000 Version: 2 (Draft 3) Mailing List: [EMAIL PROTECTED] Number: 88 =head1 DRAFT STATUS This redaction has been modified to reflect Pete