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?
Although the error-traceback output in recent versions of Chicken
is helpful, the output can still be rather dense, and finding the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 25, 2006, at 4:35 PM, Graham Fawcett 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?
Although the error-traceback out
On 5/26/06, Kon Lovett <[EMAIL PROTECTED]> wrote:
On May 25, 2006, at 4:35 PM, Graham Fawcett 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?
Don't think there is a di
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
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
On 5/29/06, Graham Fawcett <[EMAIL PROTECTED]> wrote:
If this is useful to anyone else, I'll make an egg out of it.
Sure. Eggs, eggs, eggs is what we need.
(felix)
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/m
