This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Howdy -- great question! The idea that it is "not appropriate" to validate arguments to a public method (as opposed to it being "appropriate" to validate args to a private method) is because with a *public* method, you're exposing that method to the outside world, so you had better be taking care of the validation in your code (including use of exceptions if necessary). In other words, if the method is public, then code *you* did not write and cannot control can invoke that method, so you must protect it with programmatic validation. But... if it is a *private* method, then *you* are the only one who is writing the code that invokes that private method, so it's OK to use assertions to test what you are assuming that *you* have sent in. So that's the main difference. Remember that both are legal (can compile and run), but the exam expects you to know what is and is not an "appropriate" use of assertions, and this is one example (public vs. private method arg validation). Cheers, Kathy (working on becoming more assertive )