Lab

All the C programs you write for this class should follow the well established good C coding conventions. If you turn in code that deviates from these conventions, you may not earn full credit for your solutions.

Your work MUST be handed in as git submissions to your repository for this class. Be sure to observe the name of the repository and to grant developer access to the instructors and all the class TAs. As a matter of practice, you are expected to:

• Add your solutions (to lab or pre-lab) periodically to your own repository. This will ensure that it will be possible to restore your correct work, if you happen to inadvertently break a solution that was working fine.
• Be sure to add, commit, and push all the files that you are asked to write or modify in a given assignment. Don’t expect the assignment to enumerate all the names of the files you should submit! Rule of thumb: if you worked on something, add it to your git repo.
• If you ever get your git repo in a corrupted state, it is your responsibility to fix it or to ask for help to fix it.

Labs are due on the due date listed, before the lab on that date. Lastly, note that the schedule is under active revision, so that topics may shift (though likely not permute :). Also note that the link to the lab does not open until the day of the lab.