From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-user@gnu.org
Subject: Re: How to add Guile support to a package
Date: Mon, 5 Jan 2015 13:18:11 +0000 [thread overview]
Message-ID: <20150105131811.766a8813@bother.homenet> (raw)
In-Reply-To: <4850D445-1C26-4463-9D95-3883943E438A@telia.com>
On Mon, 5 Jan 2015 11:05:31 +0100
Hans Aberg <haberg-1@telia.com> wrote:
>
> > On 5 Jan 2015, at 10:19, Antonio Ceballos <aceballos@gmail.com>
> > wrote:
>
> > GNU Chess has not been using the garbage collector so far.
>
> There is an issue when using C++ global objects having initializers
> doing allocations, on platforms (as on OS X) where the GC initializer
> must run first.
Does this include guile-2.0? That uses the gc library, which seems to
require some precautions to be taken on Darwin as regards the loading
of dynamic libraries, but I have not heard of problems interfacing with
static global objects where those static objects are conventionally
allocated rather than GC'ed.
In any event, I have not had problems getting guile to work as an
optional extension language for a C++ program with linux, from the
memory allocation point of view. There are however issues with
accommodating guile exceptions, which are basically long jumps, to
C++ objects with non-trivial destructors. You have to organize the
code so that no guile exception can take such a C++ object out of
scope, and no C++ exception can propagate out of a guile dynwind block.
Chris
next prev parent reply other threads:[~2015-01-05 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 9:19 How to add Guile support to a package Antonio Ceballos
2015-01-05 10:05 ` Hans Aberg
2015-01-05 13:18 ` Chris Vine [this message]
2015-01-05 14:44 ` Hans Aberg
2015-01-05 16:27 ` Chris Vine
2015-01-05 17:06 ` Hans Aberg
-- strict thread matches above, loose matches on Subject: below --
2015-01-04 13:47 Antonio Ceballos
2015-01-04 15:03 ` Matt Wette
2015-01-05 9:59 ` John Darrington
2015-01-05 17:08 ` Ludovic Courtès
2015-01-05 17:34 ` Antonio Ceballos
2015-01-05 19:45 ` Ludovic Courtès
2015-01-06 10:26 ` Antonio Ceballos
2015-01-06 20:16 ` Hans Aberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150105131811.766a8813@bother.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).