Xref: utzoo comp.lang.c:24499 comp.edu:2784
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!cs.utexas.edu!asuvax!noao!arizona!robert
From: robert@cs.arizona.edu (Robert J. Drabek)
Newsgroups: comp.lang.c,comp.edu
Subject: A 12-hour C seminar
Message-ID: <16111@megaron.cs.arizona.edu>
Date: 13 Dec 89 15:03:19 GMT
Organization: U of Arizona CS Dept, Tucson
Lines: 30


Sometime soon I will be giving a 12 hour course on C programming
directed towards the working programmer.  (It's a non-credit evening
course.)

What I would like
   => through email and not follow-up articles
   => from people who have either taught or taken a similar class
is a suggested set of topics--things which definitely should not be left
out (and maybe those things which should be left out because of time
constraints or other good reasons).

I do not expect to make this a course in software engineering or data
structures as I hope they already have the background, but I do want to
cover all important C-related topics.  All operators, control
structures, types, reserved words, standard functions and libraries (can
I really expect to hit most of the common functions?) are on my list.  I
plan on using ANSI C from K&R 2--reasonable?  The common errors which
beginning (and even knowledgeable) C programmers make are on my list--
maybe you have your favorites you would like to share.  Is there a
particular order you prefer to present topics to reduce confusion and to
speed up the process?

I welcome any good streams of thought, but the technical ones from your
own experiences will be the most useful.
-- 
Robert J. Drabek                            robert@cs.Arizona.EDU
Department of Computer Science              uunet!arizona!robert
The University of Arizona
Tucson, AZ  85721