meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
up_to_here [2020/09/27 13:10] – revuskyup_to_here [2020/12/23 10:09] – [The up-to-here marker in parsing productions] revusky
Line 1: Line 1:
 ===== The "Up-to-here" Marker ===== ===== The "Up-to-here" Marker =====
  
-The //up-to-here// marker ''=>||'' and the //up-to-here-plus// marker ''=>|+n'' (where n is an integer) was introduced to be able to express [[lookahead]] in a more succinct and less err-prone manner than using the legacy ''LOOKAHEAD'' or even the terser ''SCAN'' statement.+The //up-to-here// marker ''=>||'' and the //up-to-here-plus// marker ''=>|+n'' (where n is an integer) were introduced to be able to express [[lookahead]] in a more succinct and less err-prone manner than using the legacy ''LOOKAHEAD'' or even the terser ''SCAN'' statement.
  
 Where in legacy JavaCC, you would write: Where in legacy JavaCC, you would write:
Line 67: Line 67:
 </code> </code>
  
-This means that we scan up to (and including) the "bar" token when the expansion at a [[choice point]] starts with ''Foobar''.+This means that we scan up to (and including) the "bar" token when the expansion at a [[choice points|choice point]] starts with ''Foobar''.
  
 Now, the choice construct above can be written simply as: Now, the choice construct above can be written simply as: