www.cs.colorado.edu/~main/cs1300/lab/
- G++ and Emacs
- Using GDB from within Emacs
- Loops and the BGI Graphics for G++
- Parameters
- File Input and Output
- Using the Make Facility
Exams
The purpose of the exams is to ensure that you
have a basic understanding of the
material that's required to take further computer science courses.
With this in mind, we'll provide you with precise study guides for
each exam. In order to move on to the next computer science course
(with a grade of at least C- in CSCI 1300), you must have strong
performance on these exams and do a certain amount of the programming
homework. For better a better course grade (an A or B), you must also
complete significant additional programming projects (as described in
the
Grade Guide at
www.cs.colorado.edu/~main/intro/grading.html).
Please read the course syllabus (
www.cs.colorado.edu/~main/intro/syllabus.html)
for a listing of the exam dates.
- Exam 1 (100 points). In-class multiple choice exam early in the semester,
to test that you are keeping
up with the reading and homework.
- Exam 2 (50 points). Programming exam
during your recitation.
- Exam 3 (50 points). Programming exam
during your recitation.
- Exam 4 (50 points). Programming exam
during your recitation.
- Exam 5 (50 points). Programming exam
during your recitation.
- Exam 6 (50 points). Programming exam
during your recitation.
- Exam 7 (50 points). Programming exam
during your recitation.
- Final Exam (150 points).
The final programming exam
is during final exam time that is listed for your recitation time
(not for your lecture time) and will be held in your recitation room.
Final exam times are online at
www.colorado.edu/Academics/academic_cal.html.
Supplements
Course Policy
In order to effectively learn how to program,
all work that you submit in this class must be entirely your own.
In particular:
-
You MAY talk with other people about the assignments and the
high-level design of a solution.
-
Other people MAY answer questions, including writing a couple lines of code
with pencil and paper to show you the syntax of some programming feature.
-
If you receive such help, you MUST include the name and email address
of the other person in clear comment at the top of your program.
This includes tutors that you hire (please show this policy to any tutor).
-
You MUST NOT look at any other person's program on a printout or
screen before completing and submitting your own work.
-
You MUST NOT work together with another person, devising just one
solution between the two of you.
-
You MUST NOT copy any part of any other person's files, not even
to use the copy as a "reference".
Breaking these rules will result in an F for the entire course.