Timeline for How to teach Exception Handling for New Programmers?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2010 at 19:01 | comment | added | Matthieu M. | right, that's why you got my +1. I just felt your answer could be interpreted as "never use another mechanism" :) | |
| Nov 4, 2010 at 18:56 | comment | added | dsimcha | @Matthieu: Right. But if you understand what historical problems exceptions are meant to solve, rather than learning about them in a vacuum, it becomes more obvious that it's silly to use them for non-exceptional situations. | |
| Nov 4, 2010 at 18:50 | comment | added | Matthieu M. | I agree that showing how it would be done without exceptions is good, but then comes the burden of explaining when to use exceptions and when to use other technics (because not all situations are exceptional) | |
| Nov 2, 2010 at 17:02 | comment | added | dsimcha | @Kanini: In general I think most relatively new/high level constructs seem like solutions in search of problems and are easy to use wrong if you don't understand what problem they were meant to solve and why they were invented. | |
| Nov 2, 2010 at 7:47 | comment | added | Kanini | +1 for the teaching practice of leading them in the traditional C style return codes and error numbers and showing them that it works poorly and therefore, teaching them how it will work is a brilliant! | |
| Oct 29, 2010 at 21:09 | history | answered | dsimcha | CC BY-SA 2.5 |