This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++ Patch] Fix for PR c++/19076 and PR c++/6628
- From: Jason Merrill <jason at redhat dot com>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Douglas Gregor <dgregor at cs dot indiana dot edu>, gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com
- Date: Tue, 22 Feb 2005 09:27:56 -0500
- Subject: Re: [C++ Patch] Fix for PR c++/19076 and PR c++/6628
- References: <200501222253.46148.dgregor@cs.indiana.edu><m3r7j9wj5p.fsf@uniton.integrable-solutions.net>
On 22 Feb 2005 01:08:34 +0100, Gabriel Dos Reis <gdr@integrable-solutions.net> wrote:
> Douglas Gregor <dgregor@cs.indiana.edu> writes:
>
> [...]
>
> | However, one cannot add qualifiers to a function type. For instance,
> | the second line of the following code does not add qualifiers to
> | "foo":
> |
> | typedef int foo(float) const;
> | typedef volatile foo foo_v; // #2
>
> GCC has an extension whereby
>
> volatile foo F;
>
> is legal and means that "F" cannot return. How does your patch
> interact with that extension?
This has not been true of the C++ front end for a long time. I thought
that the documentation said that, but I don't see it now.
Jason