Fire / Canvas / Schedule / Chalmers studieportal / GU ad (sv) / GU kursplan / GU course description / Course page 2020
Tuesday lectures are in HC2, with exceptions, Thursday lectures in HA1, starting at 13:15.
Material: plt = course book, dragon = Dragon book. Slides follow closely the plt book.
|Tue 02/11||13-15||PL Design, Compilation Phases||slides, plt 1, dragon 1, code|
|Thu 04/11||13-15||Grammars / BNFC / Hands-on with Lab 1||slides, plt 2, dragon 2.8.2,4.1-4.3, live coding start|
|Tue 09/11||13-15||Formal languages and parsing||slides, plt 3, dragon 3,4, LL parser code LR-table.txt|
|Thu 11/11||13-15||Theory of lexing||slides, plt 3, dragon 3,4|
|Mon 15/11||23||Lab 1 deadline|
|Tue 16/11||13-15 HB3||Type checking||slides, plt 4, dragon 5,6, script prime.c|
|Thu 18/11||13-15||Interpreting||slides, plt 5, script|
|Tue 23/11||13-14 SB-H1||Hands-on with Lab 2 (Haskell)||lab2 PM script Monads|
|Tue 23/11||14-15 SB-H1||Hands-on with Lab 2 (Java)|
|Thu 25/11||13-15||Code generation||slides, plt 6, dragon 6,7, script|
|Mon 29/11||23||Lab 2 deadline|
|Tue 30/11||13-14||Hands-on with Lab 3 (Haskell)||lab3 PM|
|Tue 30/11||14-15||Hands-on with Lab 3 (Java)|
|Thu 02/12||13-15||Functional programming languages||slides, plt 7, dragon 6.5,7.3, script|
|Tue 07/12||13-15||Type inference and polymorphism||plt 7.7-9, script|
|Thu 9/12||13-14||Hands-on with Lab 4 (Haskell)|
|Thu 9/12||14-15||Hands-on with Lab 4 (Java)|
|Tue 14/12||13-15 SB-H1||Dependent types (Agda)||Live coding start|
|Wed 15/12||23||Lab 3 deadline|
|Thu 16/12||13-15||Preparing for the exam||Training exam Solution Answer Q1 Q1.c Answer Q3-6|
|Mon 10/01||23||Lab 4 deadline|
|Mon 24/01||13.30-15.00||Exam review (EDIT 6128)||Solution|
|Fri 28/01||23||Final lab deadline||all lab returns|
|Tue 12/04||8.30-12.30||First reexam|
|Thu 25/08||14-18||Second reexam|
The official course schema is in Time Edit.
The aim of the course is to give understanding of how programming languages are designed, documented, and implemented. The course covers the basic techniques and tools needed to write interpreters, and gives a summary introduction to compilation as well. Those who have passed the course should be able to
Andreas Abel, responsible course teacher and examiner.
shreyash student chalmers se(insert @ and .)
romeborn student chalmers se(insert @ and .)
Questions regarding this class (organization, content, labs) should be asked publicly on the Canvas forum in the most cases. You are also welcome to answer questions by others. (Don't give away any lab solutions when you ask or answer questions!)
Lab supervision workflow: Start a Zoom meeting and invite your group partner to join. To ask for help, sign up on the Waglys digital waiting list with your 10-digit Zoom ID (as "6435657890" from "https://chalmers.zoom.us/j/6435657890"), so that the TAs know where to find you. Please make sure your meeting does not require password to get in. A TA will join your Zoom meeting as soon as it's your turn.
Lab supervision is also available in room ED3354 on Tue, Thu and Fri.
|Tue||15:15-17:00||Zoom, ED3354||Mohammad, Andreas|
|Thu||15:15-17:00||Zoom, ED3354||Mohammad, Anna|
|Fri||13:15-15:00||Zoom, ED3354||Oskar, Anna|
The lab rooms and supervision are available from Tue 02 Nov till Fri 17 Dec 2021, except for Fri 05 Nov which is a half-day. Extra supervision sessions (Zoom) are planned for January 2022, 15:15-17:00, at the following days: Tue 18th, Wed 19th, Jan 25th, Jan 26th.
Attendance in these classes is optional. Normally, each student should attend at most one supervised laboration time each week. Since attendance is not compulsory, there may be room for more times. But, if there is lack of room, those who attend their first supervision of the week have priority to get a place and supervisor help.
There will be four laborations, written in pairs. (Individual solutions are accepted per exception, please contact the course responsible.) You have to pass the labs to pass the course. However, the course grade is determined solely by the exam.
The labs are quite substantial, so please set aside at least 30 full working hours (4 full working days) before the deadline. It is recommended to start at least 10 days before the deadline.
It is recommended to use a version control system like git for code development. In case you use cloud-based code hosting like, e.g., GitLab, GitHub, or Bitbucket, make sure your repository is private to not give away your lab solution. (Along the same lines, never post your solution on public fora and mailing lists!)
Reporting is done via Fire. Before submitting your solution, run your program through the provided test suite. Also, make sure that your submission contains all necessary files and the build succeeds. For instance, if you are submitting an archive, unpack the archive in a fresh directory and check the build there.
We guarantee two gradings per lab: one for the version submitted before the ordinary deadline for that lab, the other for a resubmission before the final deadline. If your first submission does not build or does not pass the testsuite, you will just get fails testsuite as grading.
Note: You have to submit something by the first deadline, otherwise Fire will not allow a (re)submission for the final deadline. (In the worst case, if you absolutely did not manage to work on the lab before the first deadline, submit an empty solution.)
As part of the grading, you may be asked to explain your solution in person to a course teacher. Be prepared to get a call for such an explanation meeting. In particular, make sure you understand all parts of the solution (good documentation helps!).
The written exam determines the course grade, the usual grading scales apply: Chalmers: 5, 4, 3, U; Gothenburg University: VG, G, U.
Exam dates: 13 Jan 2022 am J, 12 Apr 2022 am J, 25 Aug 2022 pm J.
The exam tests the understanding of the course contents from a more high-level view, e.g., the underlying theoretical concepts. The exam has the same structure as these old exams (download as archive).
Further, here are some old exercises and solutions to prepare for the exam.
The main book will be one that developed from earlier editions of this course:
If you are really interested in the topic, for instance, if you want to continue with the Compiler Construction course, you should also consider the Dragon book,
Both books are available at web bookshops. The main book will also be sold at Cremona.
A good (yet slightly dated) introduction to monads in Haskell, useful for implementing interpreters, type checkers, and compilers, is this article:
It also contains an introduction to parser combinators.
If you are solving the labs on your own Windows machine, you might have to obtain some
command-line developer tools stemming from the Unix world, like
(These are by default available on Linux and can be installed from Xcode on macOS.)
Windows from version 10 offers installation of a Linux distro via the
Windows Subsystem for Linux
Other options are MSYS2 and Cygwin.
We use the BNF Converter (Homepage | Hackage | Stackage | GitHub).
Download and installation instructions at https://bnfc.digitalgrammars.com/.
When using the Java backend, you will need either ANTLR or the CUP libraries and either JFLex or the JLex libraries. CUP has seen incompatible changes in its interface; thus, the version you need may depend on your BNFC version.
Download the JAVA archives for
CUP v11b runtime, and
Make sure they are placed in your classpath, for example (Linux / macOS)
by storing these jars in
$HOME/java-lib/ and adding the following line (or a suitable variant) to
(could also be
.bash_profile or similar):
You can download pre-compiled versions here.
Make sure they are placed in your classpath, for example (Linux / macOS)
by extracting to
~/javatools/ adding the following to
On Debian-style Linux (like Ubuntu), the following now also works to install these libaries:
sudo apt install jlex cup
Then the class path needs to be set as follows (bash):
Student representatives for DAT151 Programming language technology.
|MPALG||syedrahamatulla gmail com||Rahamatullah Syed|