Roger Browne wrote:
in foo handler
in main handler
in main handler
Fixed. Now the main handler catches just once.
Regards,
Roger Browne
Thanks for testing,
leo
Roger Browne wrote:
Leo, did you change the handling of P5? I have some PIR code that works
differently under 0.2.3 and 0.3.0:
The exception object iss still P5 in the handler, no changes here yet.
If you agree that the 0.3.0 behaviour is wrong, I'll file a bug report.
But the MAIN_HANDLER
On 11 July, Leopold Toetsch wrote:
> In the old calling scheme the exception object arrived as P5 in the
> handler. This doesn't really fit into the new scheme.
Leo, did you change the handling of P5? I have some PIR code that works
differently under 0.2.3 and 0.3.0:
.sub "main" @MAIN
push_eh
On Mon, Jul 11, 2005 at 01:39:08PM +0200, Leopold Toetsch wrote:
> I can see two ways to go:
>
> a) e = interpinfo .INTERPINFO_EXCEPTION
>
> b) via the get_params opcode
>
> The latter would reflect the exception call being an internal
> continuation invocation:
>
>push_eh handler
>
In the old calling scheme the exception object arrived as P5 in the
handler. This doesn't really fit into the new scheme.
I can see two ways to go:
Store the exception (or an array of unhandled exceptions) in the
interpreter and make exceptions available as:
a) e = interpinfo .INTERPINFO_EXC
