2008/8/3 Allison Randal <[EMAIL PROTECTED]>
> I just merged in the pdd25cx branch. Resolving all the conflicts took
> several hours (124 files, 1 minute or more per file...), but otherwise it
> went smoothly.
>
> The biggest changes you'll notice are the new exception system, a vastly
> reduced usage of the remaining stack (though it's not completely removed
> yet), and the fact that pushaction subs no longer fire on scope exit
> (pushaction will likely be deprecated).
>
> Keep an eye out for exception-related problems in the next couple of weeks
> before the release.
>
Ok, Lua tests pass, but the behavior has changed.
(The tests were written to check the exception message, not the full back
trace)
The pushaction allowed to retrieve the backtrace where the exception
occurred.
The backtrace from the exception handler is alway the same (docall -> main),
so it has no interest in an user point of view.
Previously :
$ ./parrot languages/lua/lua.pbc -e "error 'user_exception'"
lua.pbc: EVAL_1:34: user_exception
stack traceback:
languages/lua/src/lib/luaaux.pir:205 in function 'lua_error'
languages/lua/src/lib/luabasic.pir:336 in function 'error'
EVAL_1:34 in function '&main_10'
languages/lua/src/lib/luaaux.pir:916 in function 'docall'
lua.pir:353 in function 'dostring'
lua.pir:247 in function 'runargs'
lua.pir:120 in function 'main'
Now:
$ ./parrot languages/lua/lua.pbc -e "error 'user_exception'"
lua.pbc: _._:0: user_exception
stack traceback:
languages/lua/src/lib/luaaux.pir:920 in function 'docall'
lua.pir:353 in function 'dostring'
lua.pir:247 in function 'runargs'
lua.pir:120 in function 'main'
François.
>
> Allison
>
>
