lightweight code but it provides me with a translating framework which
is "scheme-enabled" and very similar to what usually happens in C.
It's easy to use: whenever you want something to be translated, and not
bother about charsets, simply replace:
&q
Han-Wen Nienhuys a écrit :
> In article <[EMAIL PROTECTED]>,
> Christian Mauduit <[EMAIL PROTECTED]> wrote:
>
>>The funny thing is that if I stop calling (display %my-smob) then all
>>the smobs are correctly freed when calling scm_gc().
>
>
> There
ionning in the docs that the returned
value for the free callback should reflect the amount of memory freed
that was *allocated with scm_must_malloc* and not the general amount of
freed memory.
Or maybe I'm wrong on this point, in that case I'd be curious to hear
the advices of Guile expe
rty source-me
> 'line
> )
>
> (display (list key args))
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.
Have a nice day,
Christian,
get an elegant solution to my problem, I'll try to package it and
make a short text on the question, by searching the web I found out that
I'm not the only one to wish to handle his errors himself, but the
tutorial does
t; (if such
a handler exists?) and get these errors in C, and then decide what to do
with it.
2) actually get precise error informations (file, line, source, error
description) the way the interactive Guile interpreter does.
I read the Guile manual, but:
http://www.gnu.org/software/guile/docs/guil
=bar
and it will be set. Point is the "export" command is interpreted by this
parent shell, so it has means to set in within this shell. No idea how
to do this with Guile, except setting your environnement variable from
Guile and then launch your program _from_ Guile. The way bash does 8-)
