Hi all,
I'm in the process of embedding Guile in an application and although I seem to
have the essentials working, I'd appreciate some confirmation of the validity of
my approach and also some tips on a couple of loose ends.
I won't bore you with the specifics of my application; for the purposes
Dimitris Papavasiliou schreef op di 21-12-2021 om 11:12 [+]:
> [1...]
> . The manual is not very specific about how and when finalizers are
> run. The
> approach above seems to correctly finalize all objects created as
> the Scheme
> code executes, but if references are kept, say via (d
Hi,
Maxime Devos schreef op di 21-12-2021 om 11:37 [+]:
> > approach above seems to correctly finalize all objects created
> > as
> > the Scheme
> > code executes, but if references are kept, say via (define),
> > they
> > are not
> > finalized and I get memory leaks.
You can (set! t
Maxime Devos schreef op di 21-12-2021 om 11:37 [+]:
> About finalizers: No. From the BDW-GC faq: [...]
I misread your question; this answer doesn't apply exactly to your
question. However, there still are no formal guaranteed BDW-GC will
collect everything.
Greetings,
Maxime
Hi Maxime,
Many thanks for your response; it was very helpful. Unfortunately I'm now not
so sure that I have the basics of embedding Guile more or less working and, even
worse, I'm not really sure Guile is meant to work in the way I'm trying to use
it.
The idea is that the C++ program, after som
On Tue, 21 Dec 2021, Dimitris Papavasiliou wrote:
> The idea is that the C++ program, after some initialization, loads and
> evaluates
> one or more Scheme files (provided by the user as command line arguments).
> During the course of their evaluation, these create objects on the C++ side
> (rep
release notes:
I forgot to mention in NEWS that the configure script now
also checks for the required modules (mentioned in README)
and errors out if they are not found.
Tested w/ w3m 0.5.3+git20210102 and Guile 2.2.7.
Obligatory refresher link:
https://en.wikipedia.org/wiki/Common_
