Deep Sea –- K&R Both Near and Far
Posted: Wed Dec 19, 2001 1:38 am
<center><font color=green>Deep Sea – K&R Both Near and Far</font></center>
I need to get several things into words first.
1) If you are not up to the current lecture, you are not falling behind. This is a self-paced course, and I’m announcing the next lectures to feed those who have completed the previous lesson and are craving for more. Not to worry.
2) The class project is not necessary to get a good understanding of C. Only several have started it -- and they are keeping up. The class project becomes one for those wishing to write professional code, and is a step or two above most desires. Also, after the class has progressed more and you feel comfortable using your new tools, and wish to start the class project, then that’ll be the right time for you to dive in.
3) Starting with the next series of lectures there will be imbedded mini-programs, applications for the purpose of detailing the lecture at hand.
<hr>
The near and far part:
I have scanned across a series of chapters in the first series of lectures to follow modern day programming methodologies. However, I have covered much of chapter 1 and the rest of what I will cover in that chapter will be part of the next series of lectures.
I will NOT be covering the two paragraphs that start with “Just how…” and “if you haven’t…” on page 6, They are for UNIX usage. I also will not be covering section 1.10 which starts on page 31 unless I paint myself into a corner. Modern day paradigms shy away from letting global stuff float around in different modules, rather the liberal usage of assessors and mutators is commonplace instead.
Please read and reread the second paragraph on page 34.
Please try some of the programs in chapter 1 and ask questions about any material in chapter 1 except for the aforementioned sections I will not cover.
Past, current, and near-future reference reading can be found in the following chapters/sections:
4.5, 4.6, 4.8, 4.9, 4.11
5.7, 5.8, 5.9
6.1, 6.2
7.2
Avoid 7.4 like the plague
------------------
Allen Moulton from Uechi-ryu Etcetera
I need to get several things into words first.
1) If you are not up to the current lecture, you are not falling behind. This is a self-paced course, and I’m announcing the next lectures to feed those who have completed the previous lesson and are craving for more. Not to worry.
2) The class project is not necessary to get a good understanding of C. Only several have started it -- and they are keeping up. The class project becomes one for those wishing to write professional code, and is a step or two above most desires. Also, after the class has progressed more and you feel comfortable using your new tools, and wish to start the class project, then that’ll be the right time for you to dive in.
3) Starting with the next series of lectures there will be imbedded mini-programs, applications for the purpose of detailing the lecture at hand.
<hr>
The near and far part:
I have scanned across a series of chapters in the first series of lectures to follow modern day programming methodologies. However, I have covered much of chapter 1 and the rest of what I will cover in that chapter will be part of the next series of lectures.
I will NOT be covering the two paragraphs that start with “Just how…” and “if you haven’t…” on page 6, They are for UNIX usage. I also will not be covering section 1.10 which starts on page 31 unless I paint myself into a corner. Modern day paradigms shy away from letting global stuff float around in different modules, rather the liberal usage of assessors and mutators is commonplace instead.
Please read and reread the second paragraph on page 34.
Please try some of the programs in chapter 1 and ask questions about any material in chapter 1 except for the aforementioned sections I will not cover.
Past, current, and near-future reference reading can be found in the following chapters/sections:
4.5, 4.6, 4.8, 4.9, 4.11
5.7, 5.8, 5.9
6.1, 6.2
7.2
Avoid 7.4 like the plague
------------------
Allen Moulton from Uechi-ryu Etcetera