Bug #4449
openProhibit usage of incorrect sets of type specifiers among declaration specifiers of one declaration in pointcuts
0%
Updated by Alexey Khoroshilov about 11 years ago
Evgeny Novikov wrote:
It was mentioned in #4448:
Aspectator doesn't warn when there is more then one type specifier among declaration specifiers... C standard prohibits this.
This is not an accurate statement as far as C standards allows more than one type specifier:
6.7.2 (2)
At least one type specifier shall be given in the declaration specifiers in each declaration,
and in the specifier-qualifier list in each struct declaration and type name. Each list of
type specifiers shall be one of the following sets (delimited by commas, when there is
more than one set on a line); the type specifiers may occur in any order, possibly
intermixed with the other declaration specifiers.
— void
— char
— signed char
— unsigned char
— short, signed short, short int, or signed short int
— unsigned short, or unsigned short int
— int, signed, or signed int
— unsigned, or unsigned int
— long, signed long, long int, or signed long int
— unsigned long, or unsigned long int
— long long, signed long long, long long int, or signed long long int
— unsigned long long, or unsigned long long int
— float
— double
— long double
— _Bool
— float _Complex
— double _Complex
— long double _Complex
— struct or union specifier
— enum specifier
— typedef name
Updated by Evgeny Novikov about 11 years ago
- Subject changed from Prohibit usage of several type specifiers among declaration specifiers of one declaration in pointcuts to Prohibit usage of incorrect sets of type specifiers among declaration specifiers of one declaration in pointcuts
- Description updated (diff)
Updated by Evgeny Novikov about 10 years ago
- Assignee changed from Evgeny Novikov to Fedor Kozlov
Updated by Evgeny Novikov almost 9 years ago
- Category set to Aspects parser
- Assignee changed from Fedor Kozlov to Evgeny Novikov
- Priority changed from Normal to High