Instructions

• Only this page will serve as reference.
• Make sure you have the appropriate permissions on your files and directories.
• You have to follow the submission procedures for all your exercises.
• Your exercises will be checked and graded by your fellow classmates.
• On top of that, your exercises will be checked and graded by a program called Moulinette.
• Moulinette is very meticulous and strict in its evaluation of your work. It is entirely automated and there is no way to negotiate with it. So if you want to avoid bad surprises, be as thorough as possible.
• Moulinette is not very open-minded. It won’t try and understand your code if it doesn’t respect the Norm. Moulinette relies on a program called norminette to check if your files respect the norm. TL;DR: it would be idiotic to submit a piece of work that doesn’t pass norminette’s check.
• Using an external function that is not explicitly allowed by the subject will get you a 0.
• You’ll only have to submit a main() function if we ask for a program.
• Moulinette compiles with these flags: -Wall -Wextra -Werror, and uses cc.
• If your program doesn’t compile, you’ll get 0.
• We expect your repository to be clean. This means you can only hand in the files asked by the subject, and useful files like .gitignore and README.md
• Got a question? Ask your peer on the right. Otherwise, try your peer on the left.

Advice: Do not forget to add the standard 42 header in each of your .c/.h files. The norminette check its existence anyway!

Warning: Norminette must be launched with the -R CheckForbiddenSourceHeader flag. Moulinette will use it too.