Ultimately i believe this discussion only exists because people just want to pretend that the wrong ( in this case exceptional) things dont happen in their code. They do not want to even try and attempt to address exceptions and prefer to let some top level handler take care of things. Im saying this because most if not all libraries have very little parameter checking at their public boundaries preferring the runtime to catch nulls and so on. This is obviously a problem that we have all been hit by, after all how many times have we gotten a NPE with no message rather than a nice check at the start of the public method ? In an ideal world we would catch all the right exceptions and wrap and them inside with a nice message about what went wrong. After all if i am trying to something which is supposed to be an abstraction why arent the exceptions themselves abstracted ? it boils down to laziness :)
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
