Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [rfa/dwarf] Use objfile_data mechanism for per-objfile data
Date: Thu, 01 Apr 2004 22:01:00 -0000	[thread overview]
Message-ID: <20040401220136.GA30848@nevyn.them.org> (raw)
In-Reply-To: <vt2k70z8iq0.fsf@zenia.home>

On Thu, Apr 01, 2004 at 04:57:11PM -0500, Jim Blandy wrote:
> 
> Daniel Jacobowitz <drow@false.org> writes:
> > > How about:
> > > - 'dwarf2_objfile_data_key' for the 'struct objfile_data', and
> > > - 'struct dwarf2_objfile' and 'dwarf2_objfile' for the actual
> > >   per-objfile datatype and the global pointer to the current instance?
> > > 
> > > (Is that any better?  I think suffixes like "_data" really only belong
> > > on things whose type is unspecified at the point where the name
> > > appears, like 'void *' pointers, or objects related to them.  I mean,
> > > everything is "data"; if you're going to give something a
> > > generic-sounding name, that should be because you're emphasizing the
> > > genericness of it.)
> > 
> > I don't think that's any better.  "dwarf2_objfile" implies that it's a
> > kind of objfile.  But I'm willing to use your names :)
> 
> No, no: "We striev for kwalitie."
> 
> Okay, well, how about 'struct dwarf2_per_objfile' and
> dwarf2_per_objfile'?  That's pretty close to your original names.

- 'dwarf2_objfile_data_key' for the 'struct objfile_data', and
- 'struct dwarf2_per_objfile' for the struct
- 'dwarf2_per_objfile' for the global

Sound good?

> > > The lower-case implicit-parameter macros bug me.  But I assume they're
> > > going away soon, and upper-casing them would make the patch huge,
> > > right?
> > 
> > I didn't have a particular plan in either direction.  Doing either
> > would be an easy follow-on.  Replacing them with their expansions would
> > be noisy indentation-wise, but otherwise trivial - that may be best.
> 
> I'd be happier with replacing them with their expansions.  We could
> drop the 'dwarf_' prefixes on the member names, too.

OK.  Mind if I do this later, i.e. in a few weeks?  I'm polishing the
rest of the intercu patches for submission now.

If you have a strong preference I can do it now instead.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-04-01 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 17:16 Daniel Jacobowitz
2004-04-01 20:58 ` Jim Blandy
2004-04-01 21:06   ` Daniel Jacobowitz
2004-04-01 21:58     ` Jim Blandy
2004-04-01 22:01       ` Daniel Jacobowitz [this message]
2004-04-01 22:41         ` Jim Blandy
2004-04-02  3:08           ` Daniel Jacobowitz
2004-04-02  3:47             ` Jim Blandy
2004-04-02  4:36               ` Daniel Jacobowitz
2004-04-02 19:08             ` Andrew Cagney
2004-04-02 19:23               ` 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=20040401220136.GA30848@nevyn.them.org \
    --to=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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