CS157: Intro to C, Part II
Spring 2018
Homework
| Common Excuse | Likely Response |
|---|---|
| My home internet access failed! | Use the Linux Lab on campus. |
| I didn’t know it would be this hard! | That’s why we start early. |
| C’mon—it’s only five minutes late! | You can’t even make the late period on time? |
| Lots of homework from other classes! | You’ll plan better next time. |
| I work the night before it’s due! | You start the night before!? |
| It snowed! | Yeah, it does that. |
| My apartment burned down. I have a note from a doctor. The city declared a state of emergency. CSU closed due to weather. A family tragedy occurred. | I’ll give you more time. |
The Schedule page tells you when each assignment is due. You may turn it in late for one point off. After that, late homework will only be accepted for reasons and documentation in compliance with CSU guidelines.
If you have a scheduling conflict that you regard as a valid excuse (jury duty, ROTC, marching band, etc.), then work with me in advance. I’m much less receptive when the homework is already late.
Links to the individual homework assignments are on the tab bar above.
If your homework doesn’t compile without errors, then you get zero for the assignment. Yes, ZERO, just as if you didn’t do it at all. Make really sure that your homework compiles. If you just can’t get part of your code to compile, and it’s too late to get help, then make it a comment—you might get some credit for that.
We will test your homework using c11 on Linux.
You are not required to develop your code using c11,
but that’s a good way to ensure that it works with c11.
If, for example, you develop your code using
Microsoft Visible Stegosaurus 98.6,
and you accidentally use a Microsoft-only extension to C,
then it won’t compile with c11, and you will be graded appropriately.
If you can make a case that your code is truly ANSI C, and that c11
is flawed in that it can’t compile your code, I’m willing to listen,
but that’s fighting an uphill battle.
All assignments are to be submitted electronically and are automatically time stamped, so we know when files were submitted. Logs are kept of everything, so if you try to submit files and it does not work correctly, we can look at the logs to help identify the problems.
It is your responsibility to ensure that you have submitted all the files that are required for each assignment. All files you submit should be named appropriately. If you fail to submit homework, we can’t grade it, you get a zero for the assignment.
You can submit the same file as many times as you like. The system will keep every copy, but only the most recent will be graded. If, for some reason, you want an older version to be graded, let us know.
The system will let you check in any file at all, whether it is a text file, or an executable, or a jpeg, or a video game, or a … you get the idea … so be careful what you submit!
The system will NOT alter your copy of the file being submitted. It will just send a duplicate of it for grading. Don’t worry about it harming your files—it won’t.
Every assignment has three dates associated with it:
checkin program won’t let you. This is so your beleaguered
instructor can change the assignments to match how the class is doing.
checkin program will remind you of the due
date of an assignment when you submit it. If you are before the due
date, it will let you know how much longer you have to re-sumbit a
newer version before the due date. If you are after the due date, it
will let you know that the assignment is late. Hopefully you will
still get some partial credit.
checkin program will simply not let you submit after this date.
After this date, there is no partial credit. Sorry!
However, if you would like feedback on your homework after
the drop dead date, you can email the homework to the TA and
the TA will give you feedback on how you did (but no grade!)
Use either Linux Checkin.
