Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfa] annotate blocks with C++ namespace information
Date: Tue, 15 Apr 2003 03:07:00 -0000	[thread overview]
Message-ID: <ro1ptnosbjs.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <16027.28339.641147.70506@localhost.redhat.com>

On Mon, 14 Apr 2003 22:30:11 -0400, Elena Zannoni <ezannoni@redhat.com> said:
> Daniel Jacobowitz writes:

>> I can see it either way - in symtab or in C++.  Does it make sense
>> to have cp-namespace.c for this, do you think?

> I see it more as building language specific structures, and letting
> symtabs have a pointer to those. I think the cp-namespace.c idea is
> a good compromise.

Okay, then that's what I'll do: I'll move the buildsym stuff into
cp-namespace.c, along with whatever of the stuff I was planning to add
to cp-support.c that's namespace specific.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2003-04-15  3:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-22  1:47 David Carlton
2003-03-11 17:11 ` Daniel Jacobowitz
2003-03-11 21:14   ` David Carlton
2003-03-11 21:23     ` Daniel Jacobowitz
2003-03-11 22:43       ` David Carlton
2003-03-11 22:59         ` David Carlton
2003-03-11 23:01           ` Daniel Jacobowitz
2003-03-17 22:33   ` David Carlton
2003-04-14 19:22     ` Elena Zannoni
2003-04-14 21:33       ` David Carlton
2003-04-15  2:08         ` Daniel Jacobowitz
2003-04-15  2:26           ` Elena Zannoni
2003-04-15  3:07             ` David Carlton [this message]
2003-04-15 23:12             ` David Carlton
2003-04-16  1:22               ` Elena Zannoni

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=ro1ptnosbjs.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --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