From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Lukasz Stafiniak <lukstafi@gmail.com>
Cc: Caml <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml and Boehm
Date: Sat, 11 Apr 2009 17:03:56 +0200 [thread overview]
Message-ID: <49E0B15C.6080208@starynkevitch.net> (raw)
In-Reply-To: <4a708d20904110711i199ef805h611a04d823c8fb51@mail.gmail.com>
Lukasz Stafiniak wrote:
>>
> It is a large application. They debate whether to use Boehm or smart
> pointers. They already have embedded Scheme (Guile) and are about to
> embed Python. (Guile is said to be Boehm-compatible, in some sense,
> from the next version.) It is possible that Boehm is a no-way for
> them, I asked here to investigate this.
>
My advice is always to avoid mixing several garbage collection
techniques or implementations inside the same program.
I am not sure "they" are right in embedding both Guile & Python inside
the same program. I would really avoid doing that, especially if the
application is long-running or has to be reliable.
Did you consider having a separate Ocaml program (& perhaps also a
separate Python program) which communicates with that application using
some communication channel (be it a pipe, a socket, IPC or Posix shared
memory, ...) which at least provides a separation between various GCs
and address spaces...
From what you are suggesting, "your" application seems to be a big
spaghetti system, very brittle and hard to maintain. I do know that
these are very common, but I won't like to be at your place... because
you describe a realistic, but quite nasty, situation (probably more a
management issue than a technical one).
But beware of one stuff: GC bugs are hard to find! A single bug could
mean weeks of efforts!
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next prev parent reply other threads:[~2009-04-11 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 20:13 Lukasz Stafiniak
2009-04-11 9:46 ` [Caml-list] " Basile STARYNKEVITCH
2009-04-11 10:42 ` Jon Harrop
[not found] ` <4a708d20904110511o7d390807r3d29400cf96d6f35@mail.gmail.com>
[not found] ` <49E09C2D.4080906@starynkevitch.net>
2009-04-11 14:11 ` Lukasz Stafiniak
2009-04-11 14:27 ` Jon Harrop
2009-04-11 14:40 ` Lukasz Stafiniak
2009-04-11 20:40 ` Jon Harrop
2009-04-11 15:03 ` Basile STARYNKEVITCH [this message]
2009-04-11 20:41 ` Jon Harrop
2009-04-13 9:42 ` Christoph Bauer
2009-04-13 13:15 ` Lukasz Stafiniak
2009-04-14 5:25 ` Goswin von Brederlow
2009-04-12 3:34 ` Goswin von Brederlow
2009-04-12 12:09 ` Lukasz Stafiniak
2009-04-13 17:36 ` Xavier Leroy
2009-04-11 19:17 Ed Keith
2009-04-11 20:36 ` Jon Harrop
2009-04-12 3:25 ` Goswin von Brederlow
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E0B15C.6080208@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=caml-list@inria.fr \
--cc=lukstafi@gmail.com \
/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 NNTP newsgroup(s).