Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: David Carlton <carlton@bactrian.org>
Cc: gdb-patches@sources.redhat.com, Daniel Jacobowitz <drow@mvista.com>
Subject: Re: [RFA] handling of 'operator' in cp_find_first_component
Date: Fri, 18 Apr 2003 19:47:00 -0000	[thread overview]
Message-ID: <804F2BCA-71D6-11D7-8CF6-000393575BCC@dberlin.org> (raw)
In-Reply-To: <m3brz3zkbh.fsf@papaya.bactrian.org>


On Friday, April 18, 2003, at 03:17  PM, David Carlton wrote:

> The function cp_find_first_component assumes that the string
> 'operator' as part of an operator name can only occur at the start of
> a component.  Unfortunately, this isn't true: I've recently run into
> situations where there's a templated function whose name demangles to
> something like
>
>   int operator<< <int>(char)
>
> In particular, the return type is part of the demangled name (I'm not
> entirely sure why, but that's a separate issue),

Templated functions always have the return type in the mangled (and 
thus, demangled) names.

We've actually been through this before, they are supposed to be there.
see http://sources.redhat.com/ml/gdb/2001-06/msg00227.html
(I quote the relevant part of the ABI standard)


  reply	other threads:[~2003-04-18 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 19:17 David Carlton
2003-04-18 19:47 ` Daniel Berlin [this message]
2003-04-22  3:21 ` Daniel Jacobowitz
2003-04-22 15:09   ` Daniel Berlin
2003-04-22 15:23     ` Daniel Jacobowitz
2003-04-23 23:46     ` David Carlton
2003-04-23 23:49       ` David Carlton
2003-04-24  1:13       ` Daniel Berlin
2003-04-23 23:45   ` David Carlton
2003-04-24  1:25     ` 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=804F2BCA-71D6-11D7-8CF6-000393575BCC@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=carlton@bactrian.org \
    --cc=drow@mvista.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