Searched refs:ambiguity (Results 1 – 14 of 14) sorted by relevance
12 10 ambiguity warnings. These are normal. Don't worry.
69 # Don't worry about the ambiguity messages coming from antlr
191 the ambiguity that _a_n_t_l_r was trying to overcome with
249 contribute to ambiguity.264 pccts to work hard to resolve an ambiguity. In some cases the265 ambiguity is successfully resolved after much CPU time so there290 in cases where 1,000,000 tuples were created to resolve the ambiguity.293 There were 0 tuples whose ambiguity could not be resolved295 There were 157 tnodes created to resolve ambiguity between:473 When antlr discovers that there is a lookahead ambiguity between474 two alternatives it attempts to resolve the ambiguity by searching483 During ambiguity resolution (*not* predicate hoisting) the511 During ambiguity resolution the definition of Alpha is expanded[all …]
147 contribute to ambiguity. For example:153 will cause an ambiguity report for rule "a" which will be187 the "ambiguity aid" (Item #119). The search for a bug started188 when the ambiguity aid was unable to discover the actual source189 of an ambiguity reported by antlr.194 can lead to false reports of ambiguity. The good news is that221 alternatives. It finds an ambiguity between alts 2 and 3 for ID.223 the ambiguity. In computing the first[2] set of "expr" (which is234 pccts to work hard to resolve an ambiguity. In some cases the235 ambiguity is successfully resolved after much CPU time so there[all …]
995 of lookahead for alts 1 and 2 of rule t it finds an ambiguity.
95 # Don't worry about the ambiguity messages coming from antlr
97 Item #175 fixed an asymmetry in ambiguity messages for the following1677 of lookahead for alts 1 and 2 of rule t it finds an ambiguity.
600 return rule2cause[self.ambiguity(choices)]604 rule = self.ambiguity(self.newrules[nt])625 rule = self.ambiguity(choices)649 def ambiguity(self, rules): member in GenericParser
126 # results in an ambiguity. ast.c makes sure it's a NAME.
225 digits, as that might create an ambiguity with POSIX252 would lead to ambiguity. E.g. prefer `Cayman' to339 abbreviations like `EST'; this avoids the ambiguity.
361 " 11. To avoid ambiguity and current or future incompatibility, users are\r\n"