Jonathan Scott Duff wrote:
On Sun, Aug 13, 2000 at 07:27:47PM -0700, Peter Scott wrote:
An error has text associated with it, but also a bunch of other
attributes.
So it's a structured data type... where does OOP come into play?
1. It allows you to *extend* the base type with new
Piers Cawley wrote:
Tony Olekshy writes:
Peter Scott wrote:
An exception is an 'error'. That's already a vague concept.
I'll say it's vague. There are certainly uses for an exception to
trigger non-local success, not an error at all. In fact, there are
whole programming
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 the
I think folks are forgetting that there are more than one client for
any class. Global settings should be restricted to a single setter.
The only logical single setter is main. All other clients should
be using something local.
Another reason to avoid globals, is we are designing perl6 to be
Jonathan Scott Duff wrote:
On Mon, Aug 14, 2000 at 04:09:41AM -0600, Tony Olekshy wrote:
$@-CanFoo is an example of semantics that determines whether or
not the exception is caught; stringification may be an example
of semantics that comes into play when an exception is caught.
Ah,
Evan Howarth wrote:
Tony Olekshy wrote:
Just be sure to arrange to handle exceptions while handling
exceptions.
Are you saying that the try-catch proposal automatically
handles exceptions thrown in catch and finally blocks?
Yes.
That's an interesting idea. Java, C++, and Delphi
Peter Scott wrote:
Tony Olekshy wrote:
When you want the first one, use try + catch.
When you want the second one, use eval, then manipulate $@.
Just be sure to arrange to handle exceptions while handling
exceptions.
Erk, people shouldn't have to use such radically different
Peter Scott wrote:
If anyone suggests that
try { }
catch Exception::Foo, Exception::Bar { ... }
catch { exception thrown here causes it to
start going through catch blocks again }
then I'm afraid I'm going to have to turn to drink.
Agreed. However,
This seems like a good idea, to me.
-Corwin
From: Steve Simmons [mailto:[EMAIL PROTECTED]]
IMHO trading six RFCs for two will greatly improve the chance of passing.
