In this course, you will be submitting most of your assignments electronically. We will be printing them for the TAs to mark, and we will also do a lot of automatic testing. Read and follow the following rules carefully.
We apologize for having to be so strict, but remarking takes a huge amount of time per assignment -- and with so many students, it becomes intractable.
If you violate any of the following rules then you may get a zero on some or all parts of the assignment, WITH NO APPEAL ALLOWED. (Please notice that you have to go out of your way to violate them!)
Put only one public
class in each
.java
file.
Submit your .java
files (the source code), not
your .class
files. Do NOT rename your
.class
file to make the electronic submission
work.
Don't ever use package
statements, even
if your favourite IDE inserts them automatically. Delete
them if they appear.
Capitalization matters in Java, including in filenames. This
means that class names must match the filenames exactly. For
example, if your class is called
AssignmentZero
, your file must be called
AssignmentZero.java
, and not
assignmentzero.java
or
Assignmentzero.java
. Use the capitalization
asked for in the handout and starter code.
Sometimes we will ask you to submit written answers to questions. Any submissions must be plain text only. You can easily ensure this by typing your answers in DrJava or CodeWarrior. (Important: these files MUST NOT be in Microsoft Word format.)
When an assignment specifies output, the output of your code must follow the specification precisely. This includes using exactly the capitalization, number of spaces, punctuation and line breaks specified. And you must not add anything extra to the output. Your program may be marked automatically and any output which isn't exactly as specified will receive a zero.
If you violate any of the following rules you will lose substantial style marks.
Each line must be less than 80 characters long including tabs and spaces. We will be quite strict about this.
The following line is 80 characters long. You can copy and paste it to see how long your lines of code are:
////////////////////////////////////////////////////////////////////////////////
Use a tab width of 2 (DrJava's default), if you use tabs at all. The best way to make sure your program will be formatted correctly is never to mix spaces and tabs -- use only tabs, or only spaces.
If you resubmit a file, that is the only copy we will have. Your old submission will be overwritten, including the timestamp.
It's okay to submit extra files. We will ignore all files that we didn't ask for.
You will usually get some marks if your program compiles, even if it doesn't run correctly. Thus, it is always in your best interest to turn in something that compiles.
It is possible that these rules will be overridden for particular assignments. Any such changes will be announced in class or on the web site.
Send email to CSC148H Last modified: Sun Dec 29 14:56:52 EST 2002 |