Lines Matching refs:ambiguity

1039 This models a problematic part of the C++ grammar---the ambiguity between
1084 Here, there is no ambiguity (this cannot be parsed as a declaration).
1097 Suppose that instead of resolving the ambiguity, you wanted to see all
1143 @samp{%merge} clauses.  Otherwise, the ambiguity would be unresolvable,
4193 Before reporting an unresolvable syntactic ambiguity, a GLR
4195 of that ambiguity.
4205 When a GLR parser reports an ambiguity, which of multiple candidate
4310 When ambiguity occurs, explicitly declared names may be used for values and
6809 This particular ambiguity was first encountered in the specifications of
6810 Algol 60 and is called the ``dangling @code{else}'' ambiguity.
7157 The error is an ambiguity: there is more than one way to parse a single
7218 three together make a subtle ambiguity: even an empty input can be parsed
7264 Yet this proposal introduces another kind of ambiguity!  The input
7267 @code{redirect}/@code{redirects}).  However this ambiguity is now a
7891 the result.  Otherwise, it reports an ambiguity.