Created on 2022-10-07.00:00:00 last changed 1 month ago
Suggested resolution:
Change and add before 11.4.1 [class.mem.general] paragraph 1 as follows:
member-declarator: declarator virt-specifier-seqopt pure-specifieropt declarator brace-or-equal-initializeropt
The token sequence = 0 is treated as a pure-specifier if the type of the declarator-id (9.3.4.1 [dcl.meaning.general]) is a function type, and is otherwise treated as a brace-or-equal-initializer. [ Note: If the member declaration acquires a function type through template instantiation, the program is ill-formed; see 13.9.1 [temp.spec.general]. --end note ]
Subclause 11.4.1 [class.mem.general] has this grammar:
member-declarator: declarator virt-specifier-seq[opt] pure-specifier[opt] declarator brace-or-equal-initializer[opt] pure-specifier: = 0
The primary issue is that foo = 0 matches both member-declarator productions. Secondarily, a declarator by itself is also ambiguous.
Code such as virtual FunctionType f = 0; can be valid, so disambiguation on the syntactic form of the declarator is not possible.
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-12-04 14:18:19 | admin | set | messages: + msg7085 |
2022-10-07 00:00:00 | admin | create |