meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
choice_points [2020/10/27 18:12] – revusky | choice_points [2021/02/08 18:09] (current) – ↷ Links adapted because of a move operation revusky | ||
---|---|---|---|
Line 173: | Line 173: | ||
===== More than one way to skin a cat... ===== | ===== More than one way to skin a cat... ===== | ||
- | The //definite numerical lookahead// of two tokens worked okay in the above example, but generally speaking, it is a rather crude disposition. The legacy JavaCC tool provides two other ways to specify how we resolve a choice -- when the default resolution is not good enough. In the original, somewhat inaccurate terminology, | + | The //definite numerical lookahead// of two tokens worked okay in the above example, but generally speaking, it is a rather crude disposition. The legacy JavaCC tool provides two other ways to specify how we resolve a choice -- when the default resolution is not good enough. In the original, somewhat inaccurate terminology, |
==== Syntactic Lookahead ==== | ==== Syntactic Lookahead ==== | ||
Line 233: | Line 233: | ||
In very many common usage cases, the [[up to here]] syntax removes the need to write separate // | In very many common usage cases, the [[up to here]] syntax removes the need to write separate // | ||
- | By the same token, //semantic lookahead//, | + | By the same token, //semantic lookahead//, |
- | A general rule of thumb would be to use [[up to here]] and [[lookbehind]] constructs whenever possible instead of // | + | A general rule of thumb would be to use [[up to here]] and [[contextual_predicates]] constructs whenever possible instead of // |