Chromatic <[EMAIL PROTECTED]> wrote: > On Mon, 2004-05-24 at 03:43, Leopold Toetsch wrote:
>> Yep. The main problem is that by far not all internal code paths are >> using exceptions so that you could interfer the exit handling. This >> needs of course being fixed somewhen. > Is this as simple and tedious as replacing all Parrot_exit() calls with > internal_exception() calls of the appropriate name? No. C<internal_exception> does call C<Parrot_exit>. The former should be converted to C<real_exception> with an appropriate exception object (of some exception class scheme) to carry on the relevant information to (possibly installed) user handlers. All of this is AFAIK. > -- c leo
