|
|
Homework Submission Policies |
These policies generally apply to all programming parts of homework assignments. However, particular assignments may have specific instructions, which take precedence over these. Deadlines and procedures for other parts of homework assignments or other (non-programming) assignments will be announced as necessary. Community college and TVI students: your facilitators may enforce a different procedure; be sure you know what it is.
Web submission cut-offs are given in the instructions for each homework.
Submission of submission receipts and other written/printed material should be at the beginning of lecture on the morning of the due date (or the morning before, if the due date is not a lecture day). Written and printed material may, if necessary alternatively be submitted by 1:00 p.m. on the due date in the drop box on the first floor of Sieg Hall. Papers submitted to the drop box must be sealed in an envelope large enough to hold papers without folding. Whether submitted to the drop box or at lecture, all papers must be stapled neatly. To ensure prompt grading, clearly label the envelope (or first page for lecture submission) with the following information in really, really big print:
You may lose points if you do not follow these instructions.
Barring exceptional circumstances, web submission of homework will
not be accepted after the cut-off time specified in the
instructions for the homework. Web submissions will be accepted
but marked as late for a short period of time after the due time, but
will stop working altogether after about 30 minutes. You are
encouraged, however, to complete all assignments and ask your TA if s/he has time to discuss them with you, even if you cannot receive
credit.
When you submit your program using the turn-in mechanism, we immediately compile it using MSVC 6.0. The compiler warnings and errors, if any, are copied into the "receipt" page we return to you. If you see compiler errors, your program did not compile with our compiler. It is your responsibility to figure out why, to fix your program so that it will compile, and to go through the turn-in procedure again. (In most cases, programs that compile under a non-MSVC program will compile under MSVC as well, but not always.)
Your program is not run at the time you turn it in. Instead, we run it later, while grading it.
It is possible that a program that appears to work for you may not run correctly when we grade it, even if you've been working in MSVC 6.0. The reason is that we run your programs in "Release mode", while the default mode (the one you've probably been debugging in) is Debug. Once you are past homework 2 in CSE142, you really should test you program in Release mode before turning it in, and here's how. Ignore this advice at your own peril; you may lose points if you do.
Besides simply understanding your program and convincing yourself that it has no bugs, there are two things you can do to protect yourself against bugs that show up only in Release mode. First, if you use an unitialized variable and compile with MSVC, most times it will print a warning about this. You should take such warnings seriously (although sometimes the warning is wrong, for various reasons), and fix the problem if MSVC is right.
Second, if you're using MSVC, you might want to test your program in Release mode once you have it working in Debug mode, just to make sure.