Cross Reference: /external/clang/lib/Parse/ParseDecl.cpp

Lines Matching refs:ellipsis
1486   case tok::ellipsis:
2378     TryConsumeToken(tok::ellipsis, EllipsisLoc);
4425   // A right parenthesis, or ellipsis followed by a right parenthesis signals
4428       (Tok.is(tok::ellipsis) && NextToken().is(tok::r_paren))) {
4937     //   There is a syntactic ambiguity when an ellipsis occurs at the end of a
4939     //   the ellipsis is parsed as part of the abstract-declarator if the type
4943     if (Tok.is(tok::ellipsis) && D.getCXXScopeSpec().isEmpty() &&
4953         // The ellipsis was put in the wrong place. Recover, and explain to
4962       // The ellipsis can't be followed by a parenthesized declarator. We
5192              (getLangOpts().CPlusPlus && Tok.is(tok::ellipsis) &&
5222     // An ellipsis cannot be placed outside parentheses.
5279   // Remember where we see an ellipsis, if any.
5549 /// be the location of the ellipsis, if any was parsed.
5579     if (TryConsumeToken(tok::ellipsis, EllipsisLoc))
5633       // Last chance to recover from a misplaced ellipsis in an attempted
5635       if (Tok.is(tok::ellipsis) &&
5702     if (TryConsumeToken(tok::ellipsis, EllipsisLoc)) {
5704         // We have ellipsis without a preceding ',', which is ill-formed
5711         // point out where the ellipsis should have gone.
5729       // We can't have any more parameters after an ellipsis.