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
1035 // postfix-expression: typename-specifier '(' expression-list[opt] ')'
1041 // postfix-expression: simple-type-specifier '(' expression-list[opt] ')'
1257 // These can be followed by postfix-expr pieces.
1261 /// \brief Once the leading part of a postfix-expression is parsed, this
1265 /// postfix-expression: [C99 6.5.2]
1267 /// postfix-expression '[' expression ']'
1268 /// postfix-expression '[' braced-init-list ']'
1269 /// postfix-expression '(' argument-expression-list[opt] ')'
1270 /// postfix-expression '.' identifier
1271 /// postfix-expression '->' identifier
1272 /// postfix-expression '++'
1273 /// postfix-expression '--'
1283 // Now that the primary-expression piece of the postfix-expression has been
1284 // parsed, see if there are any postfix-expression pieces here.
1309 default: // Not a postfix-expression suffix.
1311 case tok::l_square: { // postfix-expression: p-e '[' expression ']'
1312 // If we have a array postfix expression that starts on a new line and
1314 // semicolon after the base expression and that the array postfix-expr is
1443 // postfix-expression: p-e '->' template[opt] id-expression
1444 // postfix-expression: p-e '.' template[opt] id-expression
1515 case tok::plusplus: // postfix-expression: postfix-expression '++'
1516 case tok::minusminus: // postfix-expression: postfix-expression '--'
1594 // the start of a unary-expression, but doesn't include any postfix
1906 // These can be followed by postfix-expr pieces because they are
1920 /// postfix-expression: [C99 6.5.2]
2151 /// postfix-expression: [C99 6.5.2]
