public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at wasabisystems dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13447] Another demangler problem with method cv-qualifiers
Date: Fri, 19 Dec 2003 19:18:00 -0000 [thread overview]
Message-ID: <20031219184119.10146.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031219155953.13447.drow@gcc.gnu.org>
------- Additional Comments From ian at wasabisystems dot com 2003-12-19 18:41 -------
Subject: Re: New: Another demangler problem with method cv-qualifiers
Daniel Jacobowitz <drow@mvista.com> writes:
> On Fri, Dec 19, 2003 at 01:28:30PM -0500, Ian Lance Taylor wrote:
> > The mangled name is _ZNK1C1fIiEEPFivEv, which currently demangles as
> >
> > int (*C::f<int>() const)()
> >
> > That more or less corresponds to the declaration. However, I don't
> > know whether this is correct C++.
>
> I believe it's correct C++. At least, it exercises the bits of my
> parser most closely based on the standard, and I parse it exactly as
> above. The CONST_THIS gets attached to the function_arglist used for
> the method itself, not the return type.
What would it mean to attach to CONST_THIS to the return type?
Specifically, this example does not compile:
class C { public: template<typename i> int (*f())() const; };
int foo(const C c) { return (*c.f<int>())(); }
but this one does:
class C { public: template<typename i> int (*f())() const; };
int foo(C c) { return (*c.f<int>())(); }
The only change is that foo's argument is not const.
The mangled name is _ZN1C1fIiEEPFivEv which demangles to
int (*C::f<int>())()
What is the meaning of that trailing const on the first line? What
does it mean to apply a trailing const to a return type?
Ian
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13447
next prev parent reply other threads:[~2003-12-19 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 16:32 [Bug c++/13447] New: " drow at gcc dot gnu dot org
2003-12-19 16:35 ` [Bug c++/13447] " ian at wasabisystems dot com
2003-12-19 16:37 ` drow at mvista dot com
2003-12-19 18:41 ` ian at wasabisystems dot com
2003-12-19 18:57 ` drow at mvista dot com
2003-12-19 19:18 ` ian at wasabisystems dot com [this message]
2003-12-19 19:28 ` giovannibajo at libero dot it
2003-12-19 19:29 ` drow at mvista dot com
2003-12-19 21:45 ` cvs-commit at gcc dot gnu dot org
2003-12-20 0:32 ` ian at airs dot com
2003-12-20 1:59 ` dhazeghi at yahoo dot com
2004-06-28 22:34 ` cvs-commit at gcc dot gnu dot org
2004-07-01 10:59 ` cvs-commit at gcc dot gnu dot org
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=20031219184119.10146.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).