Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
cc18:labs_07 [2018/11/28 09:32] georg.schmid |
cc18:labs_07 [2018/12/16 15:55] georg.schmid |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| [[http://lara.epfl.ch/~gschmid/clp18/compiler-extensions.pdf|Project ideas]] | [[http://lara.epfl.ch/~gschmid/clp18/compiler-extensions.pdf|Project ideas]] | ||
| - | Send Georg (georg.schmid@epfl.ch) an email titled "Project selection: groups sciper#1, sciper#2, sciper#3", containing **the names of the top exactly 5** projects you would like to do, in order of descending preference. We will do our best to assign you the projects you are most interested in. | + | Send Georg (georg.schmid@epfl.ch) an email titled "Project selection: sciper#1, sciper#2, sciper#3", containing **the names of the top exactly 5** projects you would like to do, in order of descending preference. We will do our best to assign you the projects you are most interested in. |
| You will need to base your projects on one group member's repository. Discuss among yourselves and decide which one is in the best shape, and, if you haven't already, create a Git repository to collaborate efficiently. **Your email to Georg should thus also contain the URL pointing to your Git repository which we'll clone by the final deadline.** | You will need to base your projects on one group member's repository. Discuss among yourselves and decide which one is in the best shape, and, if you haven't already, create a Git repository to collaborate efficiently. **Your email to Georg should thus also contain the URL pointing to your Git repository which we'll clone by the final deadline.** | ||
| Line 25: | Line 25: | ||
| ===== Project Proposal ===== | ===== Project Proposal ===== | ||
| - | **Deadline: Tuesday, Dec 18th 2018, 23h59** | + | **Deadline: Sunday, Dec 16th 2018, 23h59** |
| - | When the bidding phase is over and a project has been assigned to your group, you should prepare a 8-10 minutes presentation describing: | + | When the bidding phase is over and a project has been assigned to your group, you should prepare an 8-10 minutes presentation containing: |
| - | * a basic description of the features you want to add to the compiler and/or to the language | + | * a basic overview of the features you want to add to the compiler/language |
| * some (short) programs highlighting the use of these features, with a description of how your compiler currently behaves on them (if it supports them at all), and how the improvements will change that behavior | * some (short) programs highlighting the use of these features, with a description of how your compiler currently behaves on them (if it supports them at all), and how the improvements will change that behavior | ||
| * a sketch of the changes you will make to each compiler phase and of the potential new phases you'll have. This should not be a complete implementation plan, but it should demonstrate that you understand how to tackle the problem you chose. | * a sketch of the changes you will make to each compiler phase and of the potential new phases you'll have. This should not be a complete implementation plan, but it should demonstrate that you understand how to tackle the problem you chose. | ||
| - | You will present your idea during the lab sessions on Dec 19th/20th. **We ask that you send us our slides the night before so we streamline the process**. Please make sure to keep strictly to the 10 minute time limit as we'll be on rather tight schedule. | + | You will present your idea during the lab sessions on Dec 17th/19th/20th. **We ask that you send us your slides the night before so we can streamline the presentation session**. Please make sure to stick strictly to the 10-minute time-limit as we'll be on rather tight schedule. |
| ===== Project implementation and report ===== | ===== Project implementation and report ===== | ||
| Line 49: | Line 49: | ||
| You can submit your report (PDF and optionally sources) under a toplevel directory called ''report''. Additionally, you **must** include clearly specified runnable examples that showcase what your extension does under the ''examples'' directory. | You can submit your report (PDF and optionally sources) under a toplevel directory called ''report''. Additionally, you **must** include clearly specified runnable examples that showcase what your extension does under the ''examples'' directory. | ||
| - | Although you are not required to use this template, your report must contain at least the sections described in it with the appropriate information. Note that writing this report will take some time and that you should not do it at the last minute. This final report is an important part of the compiler project. If you have questions about the template or the contents of the report, make sure you ask them early. | + | Although you are not required to use this template, your report must contain at least the sections described in it with the appropriate information. Note that writing this report will take some time and that you should not do it in the last minute. This final report is an important part of the compiler project. If you have questions about the template or the contents of the report, make sure you ask them early. |
| A common question is "how long should the report be?". There's no definitive answer to that. Considering that the report will contain code examples and a fairly precise description of implementation, it should probably be at least 3 pages. Less would be suspicious. 6 pages is fine. We will not complain for up to 10 pages if the content is meaningful, but extra pages by themselves do not make a report better, so please use as much as you need. | A common question is "how long should the report be?". There's no definitive answer to that. Considering that the report will contain code examples and a fairly precise description of implementation, it should probably be at least 3 pages. Less would be suspicious. 6 pages is fine. We will not complain for up to 10 pages if the content is meaningful, but extra pages by themselves do not make a report better, so please use as much as you need. | ||