First question is why? Are you making systems programmers? Are you trying to ensure they have a deep understanding of how a computer works? Personally I woul

First question is why? Are you making systems programmers? Are you trying to ensure they have a deep understanding of how a computer works? Personally I would recommend teaching some simple type-less language first. This will be their 'Crutch' language, used to test out simple algorithms. Then I would teach them assembly language. Make sure they call subroutines and use pointers, but on a simple level. Like sort an array of strings. Then I would teach them the C and show how it directly and easily translates to assembly. Having done assembly they should have an easier time of pointers. As we all know, pointers is what makes the new C programmers cry. Well that and freeing the same space twice.