41–50 of 69 posts
---------------
Intro to Programming => C (GT) / C++ (UCR)
Intro to Data Structures => Java (GT) / C++ (UCR)
Advanced Data Structures => Java (GT) / C++ (UCR)
Compilers => C (GT) / C(++) (UCR)
Systems Software => ? / ?
Operating Systems => C (GT) / Java (UCR)
Database => ? (GT) / SQL (UCR)
---------------
Intro to CS: Java
Data Structures: C++
Systems: C
Programming Languages and Compilers: OCaml
Numerical Methods: Python
Programming Studio: Java + Ruby/Python/Perl + PHP/Any web framework + Language of your choice
Intro to Programming => Java
Intro to Data Structures => Java
Advanced Data Structures => Java
Compilers => OCaml
Systems Software => C
Database => MongoDB, PostgreSQL
Web => PHP
Logical Programming => Prolog
Functional Programming => OCaml
OOP => Java, then C++
Scripting => Python
- Programming I in C
- Programming II in C++
- Data Structures in C++
- Theory of PL rotated languages every semester and project had to be in a language you didn't know coming into the class. (C#, php, pl/sql)
- Software Engineering divided into groups, each group assigned a stack to implement (mine was LAMP)
- Databases pl/sql
- Compilers C/lex/yacc
- OS projects in C and assembly
- Parallel projects in C, python and mpi
- Python language class
- Scripting languages survey was always python and ruby, but rotated in something new or interesting each section.
- A COBOL section with old mainframe
- Assembly class was in MASM
No FP for undergrads. No one had to learn Java or C#, you were given the opportunity to be exposed to them through User Groups or electives, but directed classes in them were reserved for the Information Systems people over in the Business school.
--- edit: formatting
- C for an OS course
- ARM ASM for a CPU course
- creating some C# lite language for a compilers course.
- SML for a languages course
- SQL in a databases course
I was pushing to use python for the first programming language class since Java had too many magic words that confused people, but they didn't go for it anyway since internship employers still wanted java in the first years even.
Functional Programming: Haskell Imperative Programming: Scala Object Oriented Programming: Java Concurrent Programming: Scala Concurrency: CSPm Intro Algorithms: Haskell Compilers: OCaml Digital Systems: MIPS Assembler Networks: C Graphics: Java Databases: SQL, PHP (apparently...) Principles of Programming Languages: Haskell
Fortran -- Engineering classes
PL/1 -- Intro to Programming EE/CS
APL -- EE (network analysis, etc)
360 Assembler -- EE/CS systems course
PDP-8 Assembler -- EE/CS Project
PDP-9 Assembler -- EE/CS Project
Lisp -- EE/CS AI class and structure and theory of Programming languages
CLU -- EE/CS Research
Pascal -- grad school
I'm sure there were some others in there. I didn't really learn C until I started working on the Unix kernel after grad school.
1st year: Intro to programming in Prolog, and data structures in Prolog or C (student's choice).
2dn year: Everything in C, except for system level courses, in MIPS and x86 assembly.
3rd year: Mostly C and MIPS/x86 assembly, a very interesting discipline in programming paradigms teaching Lisp, Prolog, and Java.
4th year: From tis point on, the course starts to lose structure, my choice of disciplines used mostly C/C++, with specialized languages for compilers, and VLSI design. (Have you ever tried to do network programming in C? Strings are funny.)
5th year: About the same as 4th year.
In retrospect, the official list of languages teached in graduation is ridiculously small near the list of languages students were unofficially expected to know at its end.