Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
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 20:58:00 -0000	[thread overview]
Message-ID: <vt2ekr7a02b.fsf@zenia.home> (raw)
In-Reply-To: <20040401171557.GA17948@nevyn.them.org>


Wonderful!  So it turns out 'struct dwarf2_pinfo' has only one real
member, huh?  :)

I have to say, 'dwarf2_per_objfile_data', 'struct
dwarf2_per_objfile_data', and 'dwarf2_per_objfile' are not my favorite
cluster of names.  It took me a few passes to get it straight.  (Yes,
I should have gotten more sleep, but I suspect there are others who
work under the same conditions...)

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.)

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?


  reply	other threads:[~2004-04-01 20:58 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 [this message]
2004-04-01 21:06   ` Daniel Jacobowitz
2004-04-01 21:58     ` Jim Blandy
2004-04-01 22:01       ` Daniel Jacobowitz
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=vt2ekr7a02b.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.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