Re: RFC 63 (v4) Exception handling syntax

2000-08-24 Thread Ilya Martynov
On Thu, 24 Aug 2000, Peter Scott wrote: PS> From the beginning of the posting you're quoting: PS> PS> This RFC has been merged into RFC 88. The text of the last version PS> prior to the merge is left below for archival purposes only. Anyone PS> interested in browsing this for historical reasons

Re: RFC 63 (v4) Exception handling syntax

2000-08-24 Thread Peter Scott
At 07:54 PM 8/24/00 +0400, Ilya Martynov wrote: >PRL> Exceptions are objects belonging to some C class. Cing >PRL> an exception creates the object; therefore, C above is just a >PRL> class name (possibly including some C<::>). >PRL> >PRL> The C function is just syntactic sugar for creating a new

Re: RFC 63 (v4) Exception handling syntax

2000-08-24 Thread Ilya Martynov
PRL> Exceptions are objects belonging to some C class. Cing PRL> an exception creates the object; therefore, C above is just a PRL> class name (possibly including some C<::>). PRL> PRL> The C function is just syntactic sugar for creating a new PRL> exception class;it merely amounts to C<@EXCEPTI

Re: RFC 63

2000-08-19 Thread Tony Olekshy
Peter Scott wrote: > > I am willing to withdraw RFC 63 if the following parts are > included somewhere in RFC 88 in this or equivalent language: I should like to note that I would like Peter to be described as a co-author in RFC 88, whether or not RFC 63 is withdrawn. That is, with his permissio

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Tony Olekshy
Peter Scott wrote: > > If that were so, even without the ignore() function, I could just say > > sub Exception::IO::throw { 'do nothing' } > > and kill it that way. Right. Just like overriding core die. At that point you can change the semantics in such a way as to turn your code in

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Peter Scott
[Redirected to -errors] At 11:23 AM 8/16/00 -0500, you wrote: >On 15 Aug 2000, Perl6 RFC Librarian wrote: > > > =head2 Exceptions > > > > Exceptions are objects belonging to some C class. Cing > > an exception creates the object; therefore, C above is just a > > class name. C lets you subclass

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Peter Scott
At 11:52 PM 8/15/00 -0400, Chaim Frenkel wrote: > > "PS" == Peter Scott <[EMAIL PROTECTED]> writes: > > >> Please include the comments about global variables and action at a > distance. > >PS> I'm sorry, my brain is fried. Can you spell out for me what you mean in >PS> this context and I'll

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Dave Rolsky
On 15 Aug 2000, Perl6 RFC Librarian wrote: > =head2 Exceptions > > Exceptions are objects belonging to some C class. Cing > an exception creates the object; therefore, C above is just a > class name. C lets you subclass C to create them; > C appears to be a better name for a core functionality

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Graham Barr
On Tue, Aug 15, 2000 at 04:39:24PM -0700, Peter Scott wrote: > >PRL> =head2 Exception classes - ignoring > > > >PRL> Note that we could also make it possible to selectively or globally > >ignore > >PRL> exceptions, so that perl continues executing the line after the C > >PRL> statement. Just imp

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Piers Cawley
Chaim Frenkel <[EMAIL PROTECTED]> writes: > > "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > PRL> =head2 $SIG{__DIE__} > > PRL> <$SIG{__DIE__}> needs to be triggered only as a I resort > PRL> instead of firing immediately, since it messes with the mind of > PRL> this and every o

Re: RFC 63 (v3) Exception handling syntax

2000-08-15 Thread Tony Olekshy
Chaim Frenkel wrote: > > > [stuff about exceptions being self-ignorable] > > I am adamant against increasing the number of methods of creating > action at a distance. (Look at the planed removal of all the $/, etc > variables. Don't keep adding this type of problem. I agree completely. Not to p