%&p1
\begin{document}
\frame{\titlepage}
+
+%- Anything that is specific to your parser
+% - Positions Pim
+% - yard (parser combinators) Pim
+% - Implementation language Pim
+% - Elaborate diffulties and eases (Tussendoor)
+% - LL* Mart
+%- Did you split it into two phases lexing and parsing, or just one phase? Pim
+% - Why parser combinator for lexer
+%- Did you change the grammar, and if so how? Mart
+% - Standard tricks, remove left assoc, get operator assoc correct.
+% - How did you solve the problems of precedence and associativity?
+%- Does your parser stop after the first encountered error or can it go on? Pim
+% (bij Yard erin fietsen)
+% - Stops, this is design, parsing should be correct!!!1!
+%- For a couple of example programs, when you do a sequence of Mart
+% 1. parse
+% 2. pretty-print
+% 3. parse
+% 4. pretty-print
+% -- Dit gaan we met een shell scriptje doen
+%- Code metrics, loc, etc, met stomme xkcd Mart
+% How many lines of code do you have, how many hours did you work on it?
+% “Measuring programming progress by lines of code is like measuring
+% aircraft building progress by weight.”
+%
+% ― Bill Gates
+% Hoeveel uur, ook geen idee. Ook een stomme quote
+%- Did you try your parser on weird inputs, like 100 megabyte of nested Mart
+%parenthesis? 1 gigabyte?
+% - Yes, we did, didn't work out. Uses big heap and stack
+%- Problems and learned things
+%- Demonstrate your parser and pretty-printer on two or three programs that you
+% find interesting Mart (teminaldingen kun jij goed ;))
\end{document}
repositories / cc1516.git / blobdiff