Re: Towards a reasonable unwinding flow-control semantics.
[email protected] (Peter Scott) Wed, 16 Aug 2000 16:15:56 -0700
| Newsgroups | perl.perl6.language.errors |
|---|---|
| Message-ID | <[email protected]> |
At 07:10 PM 8/16/00 -0400, Chaim Frenkel wrote: > >>>>> "PS" == Peter Scott <[email protected]> writes: > >PS> 1. When an exception is thrown perl looks for the enclosing try block; if >PS> there is none then program death ensues. > >Err, if there isn't one. Don't throw the exception. Stop processing but >don't throw. You are imposing a style on your caller. ??? I don't get this at all. >A message would be appropriate (ala, die or warn) > >Also a use (within main or if it can work lexically) that would mean >die_if_exception_thrown. Would treat the main routine as if it were >wrapped in a try block that doesn't catch any exceptions. RFC 63 already states this. Uncaught exceptions at the outermost level are dies. (And there is a very close relationship between die and throw.) -- Peter Scott Pacific Systems Design Technologies