Compiler/lexical analyzer: Difference between revisions

Content added Content deleted

Inline

@@ Line 184: / Line 184: @@
 # the token value (only for <tt>Identifier</tt>, <tt>Integer</tt>, and <tt>String</tt> tokens)
 # the number of spaces between fields is up to you.  Neatly aligned is nice, but not a requirement.
+<br>
+This task is intended to be used as part of a pipeline, with the other compiler tasks - for example:
+<br><b>lex < hello.t | parse | gen | vm</b>
+Or possibly:
+<br><b>lex hello.t lex.out</b>
+<br><b>parse lex.out parse.out</b>
+<br><b>gen parse.out gen.out</b>
+<br><b>vm gen.out</b>
+<br>
+This implies that the output of this task (the lexical analyzer) should be suitable as input to any of the [[Compiler/syntax_analyzer|Syntax Analyzer task]] programs.
 {{task heading|Diagnostics}}
@@ Line 361: / Line 374: @@
 Your solution should pass all the test cases above and the additional tests found '''[[Compiler/Sample_programs|Here]]'''.
-This task is intended to be used as part of a pipeline, with the other compiler tasks - for example:
-<br><b>lex < hello.t | parse | gen | vm</b>
-<br>As such, the the output should be <b>exactly</b> as specified.
 {{task heading|Reference}}