outline voor presentatie
[cc1516.git] / deliverables / p1 / p1.tex
1 %&p1
2 \begin{document}
3 \frame{\titlepage}
4
5 %- Anything that is specific to your parser
6 % - Positions
7 % - yard (parser combinators)
8 % - LL*
9 % - Implementation language
10 % - Elaborate diffulties and eases
11 %- Did you split it into two phases lexing and parsing, or just one phase?
12 % - Why parser combinator for lexer
13 %- Problems and learned things
14 %- Code metrics, loc, etc, met stomme xkcd
15 %- How many lines of code do you have, how many hours did you work on it?
16 % “Measuring programming progress by lines of code is like measuring
17 % aircraft building progress by weight.”
18 %
19 % ― Bill Gates
20 %- Did you change the grammar, and if so how?
21 % - Standard tricks, remove left assoc, get operator assoc correct.
22 % - How did you solve the problems of precedence and associativity?
23 %- Does your parser stop after the first encountered error or can it go on?
24 % - Stops, this is design, parsing should be correct!!!1!
25 %- Did you try your parser on weird inputs, like 100 megabyte of nested
26 %parenthesis? 1 gigabyte?
27 % - Yes, we did, didn't work out. Uses big heap and stack
28 %- For a couple of example programs, when you do a sequence of
29 % 1. parse
30 % 2. pretty-print
31 % 3. parse
32 % 4. pretty-print
33 % -- Dit gaan we met een shell scriptje doen
34 %- Demonstrate your parser and pretty-printer on two or three programs that you
35 % find interesting
36 \end{document}