Colorado State University

This file defines the header for each page. An optional "icon" image (I use the textbook):

Three headers follow: ! Long name of class !! Semester !!! Schedule, replaced by the name of the current page.

CS156: Intro to C, Part I

Fall 2013

Schedule

Links to the various pages for this class:

Wish I could do this: * Schedule

Date Topics Slides Reading Homework
Mon Sep 30

What is a program?

Practice Problems

// Halley’s Comment

Wed Oct 2

Practice Problems

If it weren’t for C, we’d all be programming in BASI, OBOL, and Pasal.

Fri Oct 4
  • Discuss HW1
  • Bases, numbers, problems in C
  • Control Structures: if, switch
  • Control Structures are a lot like decision flow charts.
Control Structures

HW0 due Sunday noon

Practice Problems

There are 10 types of people in this world: those who understand binary and those who don’t.

Mon Oct 7
  • Finish if, else, and switch

HW1 due Tuesday noon; late Wednesday noon

One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs.

Wed Oct 9
  • Review HW1
  • Quiz #1
  • Loops

Loops Practice Problems

FoxTrot

Fri Oct 11
  • C99: mixed declarations & code
  • Discuss HW2
  • Finish Loops
  • Start functions

Functions Practice Problems
Self-Quiz

C is quirky, flawed, and an enormous success.
-Dennis Ritchie

Mon Oct 14
  • Finish Functions

C Reference Card

HW2 due Tuesday noon; late Wednesday noon

A programmer tells a colleague his wife just had a baby.
“Is it a boy or a girl?”
“Yes.”

Wed Oct 16
  • Today is the last withdraw day
  • Review HW2
  • Quiz #2
  • Recursive Functions
  • How to program
  • Arrays

Practice Problems: Arrays More arrays Self-Quiz

Should array indices start at 0 or 1?
My compromise of 0.5 was rejected without, I thought, proper consideration.

Fri Oct 18
  • Discuss HW3
  • Finish arrays
  • Don’t use sizeof on an array parameter.

Practice Problems: Strings (answers)

As soon as we started programming, we found to our surprise that it wasn’t as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs.

Maurice Wilkes discovers debugging, 1949

Mon Oct 21
  • Strings

HW3 due Tuesday noon; late Wednesday noon

Practice Problems: File I/O (answers)
These two strings walk into a bar and sit down.
The bartender says, “So what’ll it be?”
''The first string says, “I think I’ll have a beer quag fulk boorg jdk^CjfdLk jk3s d#f67hw%^U r89nvy~~owmc63^Dz x.xvcu”
“Please excuse my friend,” the second string says, “He isn’t null-terminated.”''

Wed Oct 23
  • Review HW3
  • Quiz #3
  • Finish Strings

If the odds are a billion-to-one against something happening, it’ll happen several times per second, on today’s computers.
-Bret McKee

Fri Oct 25
  • File I/O
  • Discuss HW4
  • i=--i; and a=b++ * b++;
  • Program Development using Morse Code:

File I/O

No, syntax isn’t a tax on booze and cigarettes.

Mon Oct 28
  • More file I/O
HW4 due Tuesday noon; late Wednesday noon
Wed Oct 30
  • Review HW4
  • Review for exam
  • Course evaluation
Fri Nov 1
  • Final Exam
    Photo ID required
    Questions will come from (or be based on) the quizzes, the practice problems, and your homework.

Page: Main.Schedule
Modified: June 02, 2013, at 05:16 PM
Wiki: pmwiki-2.2.35
CS Department
Apply to CSU | Contact CSU | Disclaimer | Equal Opportunity
Colorado State University, Fort Collins, CO 80523 USA
© 2012 Colorado State University