On 5/29/06, felix winkelmann <[EMAIL PROTECTED]> wrote:
On 5/26/06, Graham Fawcett <[EMAIL PROTECTED]> wrote:
> First, let me ask the short question: when an uncaught exception
> occurs, is there a way to prevent exception-handler code from
> appearing in the call-history report?
What you can do is the following: put the code that prints the
exception in a separate file, compile it with -d0 (so that no
debug-output appears). The invocation can be wrapped in
a ##core#app form (which is the same as a procedure-call,
but unsafe, and it doesn't generate a trace-info entry).
Here some untested code: [snip]
You're the man, Felix! Thanks, that was exactly what I needed.
If this is useful to anyone else, I'll make an egg out of it.
Graham
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
