Probably because they don't want their students going around writing a lot of terrible code. The techniques I talked about should only be used in very performance intensive situtations - i.e. developing a codec. You're more likely to understand these kind of things if you are deep into computer architecture.
Yeah, you are probably correct, I know i programmed the codec as i was taught, i.e. OO and easy to maintain. But it does have a speed penalty.
Maybe i will continue to develop the codec as i currently am, i.e. OO and understandable such that i can then use it as reference code for when i or someone else converts it to C.
I will be learning C++ second semester this year so hopefully i will be able to start the conversion process.
hmm... maybe i should make it open source when i have a finished working version in java, so more adept C/C++ programmers can peform the conversion.