The very first text editor 3679

It depends on the clbutt, the level, and the language. In an introductory clbutt in a new language (say, a first C course or an buttembly course) the first few programs should get reduced credit for not compiling-buttembling. But after a few weeks, the student should at least have the skills to figure out syntax errors. In junior or senior level course, a program should compile.

I have never understood a student who regards a C- as just fine... never have, never will. But they sure exist.

Again, that really does depend on the course and where you are in the semester. But in general, you're right.

I'd agree that the student may not be able to get a more complicated program to work. But it ought to at least compile.

Same here. I guess part of why I'm so unconditional on code needing to compile to be worth anything is that a student whose code *doesn't* compile has failed to take advantage of my office hours and my email for a solid week (at least -- for a more complicated program, I give longer).

I try to wander through the labs at random times, and see if anybody in my clbuttes is looking frustrated. An interesting correlation is that the ones who turn in non-compiling code never seem to be in the labs when I wander through...

Yeah... once in a while I might see something that doesn't compile that looks close enough it might be worth a look to see what's going on, but my general experience is that when I see something that doesn't compile, my reaction to looking at the code is "what the hell is *this???*" The non-compiling code generally looks like beer-fueled stream of consciousness keystrokes produced at 2:00 in the morning the night before the buttignment was due. -- Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605 Department of Computer Science FAX -- (505) 646-1002