Old Announcements
| 10-18-2000 |
Discussion 8 will be a midterm review.
So please come prepared with any topics that you are uncertain
about. These topics are fair game for the midterm:
- Everything that was in lecture up to and including Disks,
- Everything that was assigned in reading up to and including COD 8.3,
- All the labs up to and including Lab 8,
- All the homeworks up to and including HW6.
|
| 09-17-2000 |
Lab 7 ...
... will make a lot more sense if you read over the C and mips
skeletons before you come to lab and before you
do the prelab.
|
| 09-17-2000 |
Lab 4 ...
... is pretty easy. If you finish early, it would be a good
idea to start working on lab 5 because lab 5 is hard.
|
| 09-10-2000 |
Regarding lab 3 ...
If you've never used spim/xspim before, you should check out the
spim manual and make a reference card of
useful commands (do the same for unix and emacs if you are shaky
on either of them). Your reference card will save you much
time later in the semester.
|
| 09-06-2000 |
The to-do list for discussion 2 ...
- Do some administrative work;
- Quickly review a bit of the number-representation material;
- Address some common c-related problems;
- Discuss the project, lab, etc, time permitting.
The point of number (3) is to try to pre-empt some of the c-related
problems that always seem to come up every semester around project-time.
If we do it right, we can save everyone (myself included) a lot of
obnoxious debugging later in the semester.
We're going to be doing a lot of hard-core coding, so bring any
C reference materials that you have!! (Like K&R or
Dan's C Survival Notes.)
|
| 09-02-2000 |
Before you come to lab 2 ...
Ok, everyone, put on your critical-thinking caps. The purpose of lab 2 is
not to test your ability to convert numbers into different bases --
we know that you can do that. Rather, the point is to introduce you to the
C programming language.
Therefore, if you want to finish the lab on-time, you should do these three
things before you come to lab: 1) write this program in the language
that you are most comfortable with (Computing languages, not English!)
including error-checking and argument handling, 2) look over over Prof.
Patterson and the TA's "C-vs-Java" notes and see which differences apply
to your code -- make sure that you know what to do about them, and 3)
get a good idea of how to use the C compiler.
If you come to lab with a clear idea of which problems
you're going to have
(even if you don't know exactly how to fix them), you'll do alright.
If you show up completely clueless, you're going to have a long night in
Soda (and there won't be as many people around to help you) ...
|
| 09-02-2000 |
Welcome to cs61C!
I apologize that there has been so much shuffling of TAs and sections. The
enrollment crush has caught us off-guard, and we are trying to arrange as
many extra TAs as possible. Please bear with us!
With that said, Prof. Patterson has informed us that the 61B requirement is
being strictly enforced this semester. If you have not taken 61B or
a similar course at another school, you need to storm over to
the CS department and demand
that they waive the requirement for you. Look under "Important Enrollment
Information" on
Gagan's page for details.
|
|
|