Lectures

Lectures take place at 1:45 p.m. on Mondays during the 2^nd quadrimester, in room R3 (B28, Montefiore Institute).

Lecture	Date	Subject	Links
1	Mon, 3 Feb 2020	Intro, first steps and batches of data	Slides	Code
2	Mon, 10 Feb 2020	Program organisation and sequential containers	Slides	Code
3	Mon, 17 Feb 2020	Library algorithms and associative containers	Slides	Code
4	Mon, 2 Mar 2020	Generic functions and custom types	Slides	Code
5	Mon, 9 Mar 2020	Managing memory and low-level data structures	Slides	Code
6	Mon, 16 Mar 2020	Defining abstract data types	Slides	Code
7	Mon, 23 Mar 2020	Objects as values	Slides	Code
8	Mon, 30 Mar 2020	Inheritance and dynamic binding	Slides	Code
9	Mon, 7 Apr 2020	C++ 11/14 + assignment feedback	Slides
-	Mon, 20 Apr 2020	3rd project + Q&A

Projects

Project	Due	Subject	Links
1	Thu, 19 March 2020	A Belote referee	Brief	Slides
2	Thu, 20 April 2020	Power 11	Brief
3	Fri, 15 May 2020	Pacoronam (group of 2)	Brief

Resources

• An example Makefile to compile C++ projects.
• Annotated Pacoronam grid image.
• Example of execution of the pacoronam game in debug mode are available here and here.
  Note that your code should not show the mesh nor the virus outside a debug mode.
  In game mode, the first sign of the virus is when an infected character enters the Sick state.
• A Virtual Machine that can be used to test your project is available here.
• Here are the instructions for installing & using the VM.
• Alternatively, you can use docker with the cffs/oopp image:

  docker pull cffs/oopp
  docker run -it -v /tmp/.X11-unix:/tmp/.X11-unix

  If you want to also share your code folder in /path/to/code, you can use:

  docker run -it -v /tmp/.X11-unix:/tmp/.X11-unix -v /path/to/code:/home/oopp/share

  The oopp user is sudoer, and its password is also oopp.

Feedback

You have received individualized feedback about your projects on the submission platform. However, as we had to keep that feedback short, here is a more detailed and better-formatted document.

Resit

You can resubmit any project for which you did not obtain 10/20, but you can elect to keep marks from the first exam session (this will be assumed if you don't resubmit a project). Project descriptions stay the same (see above).

For this resit session, all projects are individual. You can start from code written in group during last term, but your resubmission must contain (personal) improvements resulting in significant differences with the original code. Resubmiting the same code will lead to the same mark as in the first exam session, including any late penalty. Submitting worse code will result in an even lower mark.

It is worth noting that there is no guaranteed support for projects resubmitted during the resit session. This includes no guarantee that bugs in the testing scripts will be fixed nor that the platform will be maintained (i.e. you might, or might not, receive automated feedback).