Lines Matching full:postfix
179 /// Since this handles full assignment-expression's, it handles postfix
462 /// postfix-expression
623 // This handles all of cast-expression, unary-expression, postfix-expression,
631 // to handle the postfix expression suffixes. Cases that cannot be followed
632 // by postfix exprs should return without invoking
657 // postfix-expression exist, parse them now.
660 // We have parsed the cast-expression and no postfix-expr pieces are
1041 // postfix-expression: typename-specifier '(' expression-list[opt] ')'
1047 // postfix-expression: simple-type-specifier '(' expression-list[opt] ')'
1266 // These can be followed by postfix-expr pieces.
1270 /// \brief Once the leading part of a postfix-expression is parsed, this
1274 /// postfix-expression: [C99 6.5.2]
1276 /// postfix-expression '[' expression ']'
1277 /// postfix-expression '[' braced-init-list ']'
1278 /// postfix-expression '(' argument-expression-list[opt] ')'
1279 /// postfix-expression '.' identifier
1280 /// postfix-expression '->' identifier
1281 /// postfix-expression '++'
1282 /// postfix-expression '--'
1292 // Now that the primary-expression piece of the postfix-expression has been
1293 // parsed, see if there are any postfix-expression pieces here.
1318 default: // Not a postfix-expression suffix.
1320 case tok::l_square: { // postfix-expression: p-e '[' expression ']'
1321 // If we have a array postfix expression that starts on a new line and
1323 // semicolon after the base expression and that the array postfix-expr is
1451 // postfix-expression: p-e '->' template[opt] id-expression
1452 // postfix-expression: p-e '.' template[opt] id-expression
1535 case tok::plusplus: // postfix-expression: postfix-expression '++'
1536 case tok::minusminus: // postfix-expression: postfix-expression '--'
1614 // the start of a unary-expression, but doesn't include any postfix
1926 // These can be followed by postfix-expr pieces because they are
1940 /// postfix-expression: [C99 6.5.2]
2175 /// postfix-expression: [C99 6.5.2]
