On Mon, Aug 14, 2000 at 06:17:02PM -0400, Chaim Frenkel wrote: > Let us get away from the globals as much as we can. This can easily > (I think) be taken care of by having the _exception_ itself have the > uncaught handler > > $exception = Exception::whatever->new > $exception->uncaught_handler = CODEREF Except that makes the decision the thrower's, rather then the [non-]catcher's. For example, "use warnings 'none'" could become "$Exception::warnings::uncaught_handler = undef" under my proposal, but isn't doable under yours. Basicly, my idea would let you specify exception handlers, or use try{}catch{} (-ish) structures, giving try/catch first chance. -=- James Mastros
- Re: errors and their keywords and where catch can return to... Peter Scott
- Re: errors and their keywords and where catch can retu... Tony Olekshy
- Re: errors and their keywords and where catch can ... Graham Barr
- Re: errors and their keywords and where catch ... Tony Olekshy
- Re: errors and their keywords and where ca... Peter Scott
- Re: errors and their keywords and whe... Chaim Frenkel
- Re: errors and their keywords and whe... Tony Olekshy
- Re: errors and their keywords and where catch can retu... James Mastros
- Re: errors and their keywords and where catch can ... Chaim Frenkel
- Re: errors and their keywords and where catch ... James Mastros
- Re: errors and their keywords and where ca... Chaim Frenkel
- Re: errors and their keywords and where catch can ... David L. Nicol