Should I throw on null parameters in private/internal methods?

Question

I\'m writing a library that has several public classes and methods, as well as several private or internal classes and methods that the library itself uses.

In the publi

Answer 1

In my opinion you should ALWAYS check for "invalid" data - independent whether it is a private or public method.

Looked from the other way... why should you be able to work with something invalid just because the method is private? Doesn't make sense, right? Always try to use defensive programming and you will be happier in life ;-)