On 04/17/2012 03:55 PM, Jason Merrill wrote:
I have various thoughts:
It's odd that we still treat 'return' as starting a function body long
after we removed that extension.
Maybe we shouldn't look for a function body if we already have an
initializer and aren't dealing with a function decla
I have various thoughts:
It's odd that we still treat 'return' as starting a function body long
after we removed that extension.
Maybe we shouldn't look for a function body if we already have an
initializer and aren't dealing with a function declarator.
I guess we should set initializer_tok
Hi,
I had a look to this Segmentation fault in cp_parser_member_declaration
and what happens is that initializer_token_start is still null (as
initialized) when we get to:
if (initializer)
error_at (initializer_token_start->location,
"pure-specifier on
