Skip to content
Snippets Groups Projects
Commit aa477dc6 authored by Viktor Kuncak's avatar Viktor Kuncak
Browse files

updates after lecture 1

parent 54431398
No related branches found
No related tags found
No related merge requests found
Showing
with 4 additions and 6 deletions
# Pdflatex stuff
*.log
*.out
*.aux
......@@ -17,10 +17,10 @@ The grade is based on a midterm (30%) as well as team project work (70%). Please
| :-- | :-- | :-- | :-- | :-- | :-- | :-- | :-- |
| 1 | Wed | 19.02.2025 | 13:15 | BC 01 | Lecture 1 | [Intro to CLP](https://mediaspace.epfl.ch/media/01-01%2C+Intro+to+Computer+Language+Processing/0_okro5h0v) [(PDF)](info/lectures/lec01a.pdf), [Formal languages](https://mediaspace.epfl.ch/media/01-02%2C+Formal+Languages/0_segfj94w) [(PDF)](info/lectures/lec01b.pdf) |
| | Fri | 21.02.2025 | 13:15 | ELA 2 | Lecture 2 | [Operations on Formal Languages](https://mediaspace.epfl.ch/media/02-01%2C+Operations+on+Formal+Languages/0_otyeghg6), [Regular Expressions and Idea of a Lexer](https://mediaspace.epfl.ch/media/02-02%2C+Regular+Expressions+and+Lexer+Idea/0_th59v9kx) |
| | Fri | 21.02.2025 | 15:15 | ELA 2 | Lab 1 | Interpreter |
| | Fri | 21.02.2025 | 15:15 | ELA 2 | Lab 1 | Interpreter lab released (due in 1-2 weeks) |
| 2 | Wed | 26.02.2025 | 13:15 | BC 01 | Lecture 3 | [First Symbols. Constructing a Lexer](https://mediaspace.epfl.ch/media/03-01%2C+First+Symbols.+Constructing+a+Lexer/0_a943fw0n), [From Regular Expressions to Automata](https://mediaspace.epfl.ch/media/03-02%2C+From+Regular+Expressions+to+Automata/0_icjqhfj0) |
| | Fri | 28.02.2025 | 13:15 | ELA 2 | Exercise 1 | Languages, Automata and Lexers |
| | Fri | 28.02.2025 | 15:15 | ELA 2 | Lab 2 | Lexer |
| | Fri | 28.02.2025 | 15:15 | ELA 2 | Lab 2 | Lexer lab released |
## Books
......
......@@ -13,6 +13,8 @@ The work has many aspects: the implementation in [Scala](https://www.scala-lang.
* 10% Lab 5
* 20% Lab 6 (Compiler extension, customized, the final team work statement)
After you receive your points for the submitted lab, you are allowed to discuss the lab with other group members and with teaching staff, so that you can correct it and continue to use your code in subsequent labs.
Please note that, after the lab deadline, we reserve the right to ask you to explain any code that you submitted for the lab. You need to understand all the code submitted, regardless whether you or another group member wrote it. We will let you know in advance when you need to be present in the labs or exercises for such oral explanations on your laptop. Taking this into account, you are welcome to write and submit comments explaining what your code does.
To monitor whether everyone is doing their share of work and help ensure that group members work together, we ask each student to submit via email their teamwork statement, twice during the semester: once right after Lab 3 is due, and once at the end of the semester. Please read carefully the [Teamwork Statements](teamwork.md) email instructions.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment