On the third day, you define the concrete and abstract syntax for the !MiniJava language. 

---++ Syntax Definition

You should build the syntax definition step by step. As a syntax definition formalism, you can choose either [[http://homepages.cwi.nl/~daybuild/daily-books/syntax/2-sdf/sdf.html][SDF]] or the [[Spoofax.TemplateLanguage][Template Language]].

---+++ Lexical Syntax

Start with the lexical syntax definition including identifiers, integer, and simple layout.
First, define lexical syntax rules.
Second, define follow restrictions to ensure longest matches.
Finally, use rejection rules to rule out [[http://docs.oracle.com/javase/tutorial/java/nutsandbolts/_keywords.html][reserved words in Java]].

<table style="border: 2px solid #D0D0D0; padding: 5px; width: 80%; background-color: #f0f9ff; margin-left:auto; margin-right:auto; border-spacing: 5px"><tr><td>
%T% _Tip:_ You need to define lexical syntax rules for =INT= and =ID=. For grading, it is required to comply with these sort names literally.
</td></tr>
</table>

---+++ Context-free Syntax
 
Continue with the context-free syntax of the language. 
Use the context-free grammar from the book as a reference. 

<iframe frameborder="0" scrolling="no" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; " src="http://books.google.com/books?id=JNs6fWkJZbAC&lpg=PP1&dq=modern%20compiler%20implementation%20in%20java&pg=PA484&output=embed" width="600" height="800"> width="600" height="800"></iframe>

First, define context-free syntax rules.
Next, add constructors for abstract syntax trees to your rules. 
Complete the definition with appropriate disambiguation rules.

<table style="border: 2px solid #D0D0D0; padding: 5px; width: 80%; background-color: #f0f9ff; margin-left:auto; margin-right:auto; border-spacing: 5px"><tr><td>
%T% _Tip:_ You need to define context-free syntax rules for the following sorts: =Program=, =MainClass=, =ClassDecl=, =VarDecl=, =MethodDecl=, =Type=, =Statement= and =Exp=. For grading, it is required to comply with these sort names literally.
</td></tr>
</table>

---+++ Comments

Finally, you should add lexical syntax rules for comments to your syntax definition.
Start with simple line comments.
Continue with simple block comments and extend them to support nested comments.
Do not forget to define follow restrictions.


---++ Testing the Syntax Definition

After each step, you can check your progress by building the project and running your test cases.
Therefor, you need to declare the same start symbols in your syntax definition as in your test suites.
To also test your !MiniJava editor interactively, you need to specify the start symbols also in the main editor description =editor/MiniJava.main.esv=.
You can also use _Show AST_ in the editor's _Transform_ menu to test your abstract syntax definition interactively.

<center>
http://strategoxt.org/pub/Spoofax/Features/show-abstract-syntax.png
</center>

While you extend your syntax definition step by step, it is very handy to have multiple start symbols.
But in the end, =Program= should be the only start symbol.
This will break many of your test suites. 
You can fix this by removing start symbol declarations in these test suites. 
Instead, you need to specify a setup header and footer to embed your test cases into a complete !MiniJava program.

<verbatim>
module example
language MiniJava

setup MiniJava program header [[...]]

test ...
test ...

setup MiniJava program footer [[...]]
</verbatim>

<!--
On the third day, you add syntactic editor services to your !MiniJava editor. 
Start with an outline view showing classes with their fields and methods including parameters, variable declarations and types. 
Next, add content folding for class and method declarations as well as for if-, while- and block statements. 
Finally, complete your work with a number of code templates.

---++ Editor Services

You can specify editor services for your !MiniJava editor in the following files:

	* outline view: =editor/MiniJava-Outliner.esv=,
	* code folding: =editor/MiniJava-Folding.esv=,
	* code templates: =editor/MiniJava-Completion.esv=.

These files import files which were generated from your grammar. 
In the generated files you also find some documentation about editor service specifications.

<table style="border: 2px solid #D0D0D0; padding: 5px; width: 80%; background-color: #fff9f0; margin-left:auto; margin-right:auto; border-spacing: 5px"><tr><td>
%GS% _Challenge:_
Outline the main class with the main method and its parameter similarly to an ordinary method of an ordinary class.
Therefore, the abstract syntax tree for the main method needs to be structured similarly to abstract syntax trees of ordinary methods.
Change your syntax definition to achieve this.
</td></tr>
</table>