What would an ideal intro or "crash" course in C look like? Would they differ? Based on goal of reading or writing?
Then do as much as makes sense (student interest, time available, etc.) without strings - expressions, conditionals, loops, functions, ...
-
-
TA'ing an OS course with C beginners, they really needed to learn defensive programming: 1) Reading docs for function 2) Handling every return value 3) Cleaning up even in error conditions 4) Returning unsuccessfully appropriately from the current function.
-
Defensive programming is such a key part of how you write C properly. It also teaches good reasoning about code and forces students to actually think about every single case. The students I TA'd had not learned this skill, and my attempt at requiring it was somewhat unsuccessful.
-
This is true for most/all languages. "Doesn't require defensive programming" is kinda the holy grail of language design.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.