Peter Scott wrote:
>
> try {
> } catch Exception::IO with {
> } catch Exception::Socket with {
> } otherwise {
> };
Jonathan Scott Duff wrote:
>
> try {
> } catch {
> switch ($EXCEPTION->name) {
> case IO { ... }
> case Socket { ... }
> }
> }
>
> The catch clause would catch all exceptions. The one
> thrown would be placed in a "global" $EXCEPTION variable.
With the approach proposed in RFC 88 (Structured Exception
Handling Mechanism), you could write that as:
try {
} catch {
switch ($_[0]->name) {
case IO { ... }
case Socket { ... }
}
}
There is no need for a "global".
Let's take this discussion to [EMAIL PROTECTED],
and give it a new subject.
Yours, &c, Tony Olekshy
[EMAIL PROTECTED]
- Re: RFC 80 (v1): Exception objects an... Graham Barr
- Re: RFC 80 (v1): Exception objects and cl... Peter Scott
- Re: RFC 80 (v1): Exception objects an... Jeremy Howard
- Re: RFC 80 (v1): Exception objects an... Graham Barr
- Re: RFC 80 (v1): Exception objec... John Porter
- Re: RFC 80 (v1): Exception o... Graham Barr
- Re: RFC 80 (v1): Exception o... John Porter
- Re: RFC 80 (v1): Exception o... Peter Scott
- Re: RFC 80 (v1): Exception o... Graham Barr
- Re: RFC 80 (v1): Exception objects and classes fo... Jonathan Scott Duff
- Re: RFC 80 (v1): Exception objects and classes for bui... Tony Olekshy
