On 04/09/12 13:44, Andy Wingo wrote:
So, can I eliminate this stuff and still get what I need?
On Guile 2.0, I think so, as far as I know. If you are still supporting
1.8, of course, you need #ifdeffery.
Thanks, Andy!
I still have to support 1.6. 1.8 is not going away any time soon.
Cheers
On Mon 09 Apr 2012 13:00, Bruce Korb writes:
> Hi Ludovic,
>
> On 04/09/12 10:29, Ludovic Courtès wrote:
>>> Is this the currently accepted way of setting up an
>>> environment where I can trace errors back to their source?
>>
>> Currently uncaught errors lead to Guile printing a backtrace, norma
Hi Ludovic,
On 04/09/12 10:29, Ludovic Courtès wrote:
Is this the currently accepted way of setting up an
environment where I can trace errors back to their source?
Currently uncaught errors lead to Guile printing a backtrace, normally.
Doesn’t it work for you?
The honest truth? I found I h
Hi Bruce,
Bruce Korb skribis:
> Then I have a question: Is this the currently accepted way of setting
> up an environment where I can trace errors back to their source?
Currently uncaught errors lead to Guile printing a backtrace, normally.
Doesn’t it work for you?
Thanks,
Ludo’.
On 04/07/12 14:16, Ludovic Courtès wrote:
Hi Bruce,
(system vm trace) appeared in Guile 2.0.
Hi Ludovic,
Then I have a question: Is this the currently accepted way of setting
up an environment where I can trace errors back to their source?
char fmt[] = "(use-modules (%s))\n"
"(r
Hi Bruce,
(system vm trace) appeared in Guile 2.0.
Thanks,
Ludo’.
