From: Austin Clements <amdragon@mit.edu>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: Bertram Felgenhauer <bertram.felgenhauer@googlemail.com>,
notmuch <notmuch@notmuchmail.org>, Bart Massey <bart@cs.pdx.edu>
Subject: Re: Memory management practices
Date: Wed, 7 Sep 2011 23:05:19 -0400 [thread overview]
Message-ID: <CAH-f9WveBfvmv2jOF+C81OeeQJt06g6U0q3J_idHrs60DLw7+g@mail.gmail.com> (raw)
In-Reply-To: <CAH-f9WsfHUm_D-+wB89Lt9Wt=hjwDyywvJTK-0NwmHRg0TUsxQ@mail.gmail.com>
On Wed, Sep 7, 2011 at 10:48 PM, Austin Clements <amdragon@mit.edu> wrote:
> *snip*
>
> I'm a bit confused by the reference tree you drew. The references in
> the underlying libnotmuch objects are the other way around.
> notmuch_query_t holds a talloc reference to every notmuch_messages_t
> it produces, not the other way around.
Sorry, I went back and re-read your earlier messages and now I see why
your references were the way they were. I stand by the rest of my
previous message though. I think the technique used in the Python
bindings only works because Python's GC happens to finalize in a
particular order (though I doubt that's guaranteed, and could easily
not be the case if you stray into the realm of its cycle collector).
In general, it seems like approach is trying to recreate C-like memory
management and is fragile as a result, whereas talloc should, I think,
allow bindings to express their runtime's memory management rather
naturally.
next prev parent reply other threads:[~2011-09-08 3:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 16:32 Memory management issue in notmuch-haskell bindings Ben Gamari
2011-08-28 21:27 ` Bug in GC's ordering of ForeignPtr finalization? Ben Gamari
2011-08-29 3:26 ` Antoine Latter
2011-08-29 3:47 ` Ben Gamari
2011-08-29 4:03 ` Antoine Latter
[not found] ` <20110829183010.GA2605@24f89f8c-e6a1-4e75-85ee-bb8a3743bb9f>
2011-08-29 20:30 ` Memory management practices Ben Gamari
2011-09-07 20:36 ` Ben Gamari
2011-09-08 2:48 ` Austin Clements
2011-09-08 3:05 ` Austin Clements [this message]
2011-09-08 13:50 ` Sebastian Spaeth
2011-09-08 15:15 ` Austin Clements
2011-09-09 9:27 ` Sebastian Spaeth
2011-09-09 17:53 ` Austin Clements
2011-09-11 21:47 ` Ben Gamari
2011-09-12 2:18 ` Austin Clements
2011-09-12 12:30 ` Sebastian Spaeth
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH-f9WveBfvmv2jOF+C81OeeQJt06g6U0q3J_idHrs60DLw7+g@mail.gmail.com \
--to=amdragon@mit.edu \
--cc=bart@cs.pdx.edu \
--cc=bertram.felgenhauer@googlemail.com \
--cc=bgamari.foss@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).