Chapter 9
Some Exceptional Exceptions
IN THIS CHAPTER
Handling errors via return codes
Using the exception mechanism instead of return codes
Plotting your exception-handling strategy
It’s difficult to accept, but occasionally application code doesn’t do what it’s supposed to do, which results in an error. Users are notoriously unreliable as well. No sooner do you ask for an int than a user inputs a double, which also results in an error. Sometimes the code goes merrily along, blissfully ignorant that it is spewing out garbage. However, good programmers write their code to anticipate problems and report them as they occur.
The C# exception mechanism is a means for reporting these errors in a way that the calling method can best understand and use to handle the problem. This mechanism has a lot of advantages over the ways that programmers handled errors in the, uh, good old days. This chapter walks ...
This chapter discusses runtime errors, not compile-time errors, which C# spits out when you try to build your program. Runtime errors occur when the program is running, not at compile time.