>I agree, in general, but I would insert one caveat: some form of assembler
>language should be included, as well as a variety of higher-level languages.
That's the way it was at UWaterloo.
But, I didn't learn IBM Assembler until 3rd year.
It was Honeywell in first year.
If I were to set up a curiculum today, it would be:
1st year: languages and elements of style
COBOL Assembler and one of PLI, FORTRAN or PASCAL.
2nd year: Modular programming and one of PLI FORTRAN or PASCAL (whichever you
didn't take last year)
3rd year: Object oriented programming, C++, JAVA, and whichever is left of the
three.
4th year: graphics, databases, web, and pick your own languages (learn on your
own).
Assembler would not be optional, but you would have any one of the four years
to pick it up.
I still think procedural languages are important to learn how to programme
before you get into OOP.
I've missed a few concepts such as:
Testing
Sorting
Code verification
And, half of Knuth.
But, not being an educator, this is my educated guess.
BUT, I do NOT believe in teaching OOP first.
IMO.
-
Too busy driving to stop for gas!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
