From: pimjager Date: Mon, 14 Mar 2016 20:27:07 +0000 (+0100) Subject: werkverdeling presentatie toegevoegd X-Git-Url: https://git.martlubbers.net/?a=commitdiff_plain;h=81f72dd30fdd6b77e2da54d68d61ce8a41280993;p=cc1516.git werkverdeling presentatie toegevoegd --- diff --git a/deliverables/p1/p1.tex b/deliverables/p1/p1.tex index 1b923bd..3984b6d 100644 --- a/deliverables/p1/p1.tex +++ b/deliverables/p1/p1.tex @@ -2,35 +2,37 @@ \begin{document} \frame{\titlepage} -%- Anything that is specific to your parser -% - Positions -% - yard (parser combinators) -% - LL* -% - Implementation language -% - Elaborate diffulties and eases -%- Did you split it into two phases lexing and parsing, or just one phase? +%- 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 -%- Problems and learned things -%- Code metrics, loc, etc, met stomme xkcd -%- 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 -%- Did you change the grammar, and if so how? +%- 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? +%- 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! -%- Did you try your parser on weird inputs, like 100 megabyte of nested -%parenthesis? 1 gigabyte? -% - Yes, we did, didn't work out. Uses big heap and stack -%- For a couple of example programs, when you do a sequence of +%- 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 +% find interesting Mart (teminaldingen kun jij goed ;)) \end{document} diff --git a/spl.prj b/spl.prj index a7a20dd..b0e9413 100644 --- a/spl.prj +++ b/spl.prj @@ -31,6 +31,7 @@ Global Link LinkMethod: Static GenerateRelocations: False + GenerateSymbolTable: False GenerateLinkMap: False LinkResources: False ResourceSource: @@ -617,7 +618,7 @@ OtherModules Fusion: False Module Name: System.OS - Dir: {Application}/lib/clean-platform/OS-Linux-64 + Dir: {Application}/lib/clean-platform/OS-Mac Compiler NeverMemoryProfile: False NeverTimeProfile: False