Lines Matching refs:ambiguity

1653 This models a problematic part of the C++ grammar--the ambiguity between
1687 there is no ambiguity (this cannot be parsed as a declaration).
1698    Suppose that instead of resolving the ambiguity, you wanted to see
1732 ambiguity would be unresolvable, and the parser will report an error
4365 reporting an unresolvable syntactic ambiguity, a GLR parser invokes
4366 `YYLLOC_DEFAULT' recursively to compute the location of that ambiguity.
4376 an ambiguity, which of multiple candidate right hand sides it passes to
4458 When ambiguity occurs, explicitly declared names may be used for values
6525 hard to do in this case.)  This particular ambiguity was first
6527 "dangling `else'" ambiguity.
6820 The error is an ambiguity: there is more than one way to parse a single
6869 together make a subtle ambiguity: even an empty input can be parsed in
6905    Yet this proposal introduces another kind of ambiguity!  The input
6908 However this ambiguity is now a shift/reduce conflict, and therefore it
7492 the merge function on the result.  Otherwise, it reports an ambiguity.