From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: Value reference counting
Date: Mon, 20 Jul 2009 13:40:00 -0000 [thread overview]
Message-ID: <20090720133040.GA2111@caradoc.them.org> (raw)
In-Reply-To: <200907201013.36183.vladimir@codesourcery.com>
On Mon, Jul 20, 2009 at 10:13:35AM +0400, Vladimir Prus wrote:
> > + /* The number of references to this value. This initially includes
> > + one reference from the value chain; if release_value is called,
> > + it converts that into a normal reference. */
> > + int reference_count;
> > };
>
> I do not fully understand this comment, specifically the "it converts
> that into a normal reference". What is "it", what is "that" and what
> is "normal reference" and where the convention happens? From your email,
> I gather it's intentional that release_value does not have to be changed,
> but I don't understand anything else :-( I am sure it's just me, but
> a better comment would be good.
"It" is release_value, and "that" is the one reference. Is this
clearer?
/* The number of references to this value. When a value is created,
the value chain holds a reference, so REFERENCE_COUNT is 1. If
release_value is called, this value is removed from the chain but
the caller of release_value now has a reference to this value.
The caller must arrange for a call to value_free later. */
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-07-20 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 19:03 Daniel Jacobowitz
2009-07-17 19:04 ` Tom Tromey
2009-07-17 19:25 ` Daniel Jacobowitz
2009-07-17 22:55 ` Tom Tromey
2009-07-20 13:30 ` Thiago Jung Bauermann
2009-07-20 13:34 ` Daniel Jacobowitz
2009-07-20 14:57 ` Thiago Jung Bauermann
2009-07-20 17:34 ` Tom Tromey
2009-07-20 19:45 ` Thiago Jung Bauermann
2009-07-20 9:55 ` Vladimir Prus
2009-07-20 13:40 ` Daniel Jacobowitz [this message]
2009-07-20 15:08 ` Vladimir Prus
2009-07-21 18:18 ` Daniel Jacobowitz
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=20090720133040.GA2111@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=vladimir@codesourcery.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