From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: [python] Implement value reference counting
Date: Tue, 23 Jun 2009 16:24:00 -0000 [thread overview]
Message-ID: <20090623162404.GA24593@caradoc.them.org> (raw)
In-Reply-To: <m3iqionkqf.fsf@fleche.redhat.com>
On Mon, Jun 22, 2009 at 01:15:20PM -0600, Tom Tromey wrote:
> I'm checking this in on the python branch.
>
> This implements reference counting for 'struct value'.
> This fixes a crash that was reported here. A regression test is
> included.
>
> The reference counting is a bit odd -- the "increment reference"
> operation is called "release_value", for historical reasons.
> I may change this when I submit it upstream.
Could I persuade you to submit this upstream soonish? I have another
bug I've been meaning to fix for two years, involving bitfields, that
would be much more straightforward with reference counting.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-23 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 19:15 Tom Tromey
2009-06-23 16:24 ` Daniel Jacobowitz [this message]
2009-06-23 16:27 ` Tom Tromey
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=20090623162404.GA24593@caradoc.them.org \
--to=drow@false.org \
--cc=archer@sourceware.org \
--cc=tromey@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).