Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: David Carlton <carlton@math.stanford.edu>, gdb <gdb@sources.redhat.com>
Subject: Re: [rfc] cp-symtab.c?
Date: Mon, 02 Jun 2003 19:12:00 -0000	[thread overview]
Message-ID: <20030602191227.GA11011@nevyn.them.org> (raw)
In-Reply-To: <16091.41599.3329.152064@localhost.redhat.com>

On Mon, Jun 02, 2003 at 03:16:15PM -0400, Elena Zannoni wrote:
> David Carlton writes:
>  > Elena and I were recently talking about moving
>  > make_symbol_overload_list and friends from symtab.c to some C++ file.
>  > It's not obvious to me where to put it, though; should I create a new
>  > file "cp-symtab.c" for that?  If so, should I move the parts of
>  > cp-namespace.c that deal specifically with symbol lookup (all the
>  > functions in there with "lookup" in their name, I guess) to that file
>  > as well?  My opinion is that the answer to both questions is "yes",
>  > but I wanted to check with other people first.
>  > 
>  > David Carlton
>  > carlton@math.stanford.edu
> 
> I would hold back on the new file, *for now*. I think cp-support.c
> would work.  Doing a grep for ^lookup_ in *.c throws up too many
> things that are not clearly symbol table related, but for instance
> gdbtypes and charset related. My guess is that the term 'lookup' has
> been abused, and we should introduce something more qualifying in the
> function names.

I agree.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-06-02 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 18:56 David Carlton
2003-06-02 19:10 ` Elena Zannoni
2003-06-02 19:12   ` Daniel Jacobowitz [this message]
2003-06-02 19:20     ` David Carlton

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=20030602191227.GA11011@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=ezannoni@redhat.com \
    --cc=gdb@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