This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] C++11, grammar fix for late-specified return types and virt-specifiers
- From: Ville Voutilainen <ville dot voutilainen at gmail dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 20 Jun 2012 10:57:54 +0300
- Subject: Re: [PATCH] C++11, grammar fix for late-specified return types and virt-specifiers
- References: <87fw9vxfr6.wl%ville@ville-laptop> <4FE17D37.1070004@redhat.com>
On 20 June 2012 10:35, Jason Merrill <jason@redhat.com> wrote:
> Applied, thanks. ?Note that your dg-error regexp doesn't make much sense:
>
>
> // { dg-error "expected type-specifier before 'final'||expected
> ';'||declaration doesn't declare anything" }
>
> Regular expression "or" uses a single |, so this ends up being a long way of
> writing
>
> // { dg-error "" }
Funny. The testcasewriting gcc wiki page at
http://gcc.gnu.org/wiki/TestCaseWriting
suggests a double pipe. Quoth the Raven:
Should a line produce two errors, the regular expression should
include an "||" (ie. a regular expression OR) between the possible
message fragments.
If a single pipe is indeed to be used, perhaps we want to correct that
piece of documentation, lest
fools follow its advice. :)