[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> Finally, you might like to know that my guile-debugging package
>> includes a kind of Emacs display-backtrace front end. [...]
>
> That sounds nice!
>
> What are your plans wrt. to distribution of g
Hi,
Neil Jerram <[EMAIL PROTECTED]> writes:
> Finally, you might like to know that my guile-debugging package
> includes a kind of Emacs display-backtrace front end. In other words,
> when an error occurs, the stack is popped up in Emacs, and Emacs will
> pop up the source code for each frame, a
On Sun, 2005-09-11 at 22:19 +0200, Christian Mauduit wrote:
> FYI I use the following code instead, to display args:
>
> (apply format (cons #f (cons (cadr args) (caddr args
>
> Unelegant in the source, but displays things in a nicer way IMHO.
This is common enough -- requiring some argument
Hi,
> If we assume that the catch'ing lambda is always the same, then the
> stack-frames related to it should be stable. So, you should be able to
> discard the bottom n frames every time:
>
> For example:
> (lazy-catch #t
> (lambda () (+ 1 (hubert)))
> (lambda (key . args)
>
Christian Mauduit wrote:
> ...
> Well, using lazy-catch and a handler with the line:
>
> (display-backtrace (make-stack #t) some-user-string-output-port)
>
> actually got me very close from solving my problem completely. The only
> point is that the stack I obtain contains many useless things (
Christian Mauduit <[EMAIL PROTECTED]> writes:
> mmm, OK I see, indeed using:
>
> (debug-enable 'debug)
> (debug-enable 'backtrace)
>
> gave me much more detailed output, thanks for the tip.
FWIW, I use this at the start of my Scheme script (which is also
loaded by a C program - very similar overa
Alan Grover a écrit :
> My comments are for Guile version 1.6.4.
>
> To get a backtrace, you want something that does the same thing as the
> --debug option. However:
> "Using the debugging evaluator will give you better error messages but
> it will slow down execution."
> So, you don't want it in
My comments are for Guile version 1.6.4.
To get a backtrace, you want something that does the same thing as the
--debug option. However:
"Using the debugging evaluator will give you better error messages but
it will slow down execution."
So, you don't want it in production-code.
I believe this wi
Hello,
I'm currently coding a game using scheme as a scripting language. The
main program is a C program which first exports C functions to scheme
and then calls a scheme script. This scheme script is responsible for
all game logic, interaction, control, whatever, and the C functions are
low-level
