Notes for CMSC 421 -- Section 301
This page will be updated during the semester.
The information given on this page apply to students of section 301 of CMSC 421.
-
Mar 18, 2005:
-
Make sure you submit your project even if it's not quite within the
deadline or the project does not work quite right.
(No submission will result in zero points for that project! )
In order to make a decision of how to deal with the projects we
need to know what you did and have the timestamp of your project
submission. If you had problems submit a detailed description of
the problem as well and explain e.g. why you missed the deadline.
-
When you submit a problem report be as specific as possible - i.e.:
include the steps you did, your directory location, error messages,
possibly code that you wrote (make sure the code is not too long -
don't send any system files, instead do a diff and send a patch), ...
-
For future programming projects: it's always a good idea to make a backup
(test the backup to make sure you can use it to restore your files!)
of your existing working system and the files you are about
to edit before making major changes that could corrupt the system.
In the worst case of a major system crash you can restore quickly
from a backup and start from the point before your problem ocured.
-
Feb 02, 2005:
Ungraded assignment: (to be done before the end of Feb 2005)
-
Jan 31, 2005:
The slides that accompany the textbook, made available by the authors of the textbook: