Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] function overloading and namespaces
Date: Mon, 02 Feb 2004 20:44:00 -0000	[thread overview]
Message-ID: <yf2k735p5x2.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040202200917.GA6423@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 2 Feb 2004 15:09:17 -0500")

On Mon, 2 Feb 2004 15:09:17 -0500, Daniel Jacobowitz <drow@mvista.com> said:

> I have some deep reservations about this overload resolution code.

Yeah, me too.  I hope that my patch doesn't make that situation any
worse, but I certainly don't claim that it makes the situation
significantly better. :-(

> I am really sick of the number of variants of this C++ name parsing we
> are spawning.  While the rest of the branch will be some time yet
> maturing, I will try to merge the relevant pieces of drow-cplus-branch
> in the very near future.  Then we can dispense with this function.

Glad to hear it.

> I'm also pretty tired of the growth of functions which concatenate
> names with "::", or tear them apart with cp_find_next_component.  We
> need to use some more efficient structure for describing namespaces
> than this.  My personal hope is that we can un-flatten the symbol table
> eventually, and have dictionaries per scope.

Sounds good to me...

Thanks, committed (with Eli's ChangeLog tweak).

David Carlton
carlton@kealia.com


      reply	other threads:[~2004-02-02 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 17:58 David Carlton
2004-01-31  7:54 ` Eli Zaretskii
2004-02-02 16:32   ` David Carlton
2004-02-02 20:09 ` Daniel Jacobowitz
2004-02-02 20:44   ` David Carlton [this message]

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=yf2k735p5x2.fsf@hawaii.kealia.com \
    --to=carlton@kealia.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