Announcements

If your appeal did not get answered by mistake or you just forgot to send one, you have one last chance to appeal. this is regarding to the programming assignments and to the compiler only.

1. The final and last deadline for appeals is Thursday 11/3 13:00.
2. The only way to appeal is to email the grader: orcas at cs-bgu-ac-il.
3. The email's subject must start with "comp101: group 12345" where 12345 is replaced with your group number.
4. You must state exactly what you are appealing on (hw4 / compiler), and exactly and in detail why you think you deserve more points.
5. If the reason is that you lost a lot of points due to a small mistake, you must attach a fixed version to the email.
6. If you already emailed the grader in the past, you must send this message as a reply to the previous email.

The actual grade changes will be submitted to the faculties at a later date.

The checking reports are at http://www.cs.bgu.ac.il/~orcas/ass4/12345, where 12345 is your submission group number.

If you want to appeal on these grades, do it via the submission system only. NOT by email. the deadline for appeals is 4/3 at 13:00. later appeals will be ignored.

Please note that these grades are not related to the final project, aka "the compiler", which maybe be seen in http://www.cs.bgu.ac.il/~orcas/final/12345.

The grades are pretty good: the average of the passed submissions is 88. 32 groups got 90 or more.

Happy Purim!

Also, please don't forget to put said printout in a paper recycling bin after the frontal check is complete, thanks!

You can see the results of a single test case, "(+ 1 2)", here: http://www.cs.bgu.ac.il/~orcas/initial/12345 where 12345 is your submission group number.

If you failed in that test, you will probably get a zero for the compiler, so you will need to re-submit your work: submit a delay request in the submission system, and then submit your zip file in the usual way.
If you do this until 13:00 23/2/2010, no extra points will be deducted for late submission!

Do not submit any .o files, test files, .bak files, or any other redundant files.
Make sure you name you files correctly.
Make sure your compiler can handle compiling several files in a row, and not just one.
Make sure your code doesn't do anything when it loads (like trying to run your test cases).
Make sure you are creating the output files at the current working directory ('./'), and not anywhere else.
Makefile tips: don't use any of the following gcc flags: -O1, -O2, -O3, -g, -Wall. Instead use: -w and -Wfatal-errors. Also, make sure your default make target is a.out, and that it depends on user-scheme-code.c.

update: another very important thing to notice is that your output is the same as petite. some common mistakes are:

Changelog:
* Added id numbers
* Updated some grades (see previous message)

Students who answered "false" in 5.a will receive additional points.
Grades of students who answered "true" in 5.a will remain unchanged.

The updated excel sheet will be uploaded later.

For the exam, each group will need to come with a complete printout of the compiler.scm file, containing the entire compiler – from scanner to the code generator.

There will be three examiners and each one will test two groups simultaneously. You can sign up to one of the three examiners at these pages : Examiner1 Examiner2 Examiner3.

Please don't add yourself if your partner is already signed up.

More details will be published later.