Erik,

>This is not always true David. My framework relies heavily on hooked methods that are empty in the class definition, and over half of the code that I write at the instance level is in methods that are empty in the class definition.

Even if you are using hook patterns, you should still issue DODEFAULT(). Just because there isn't code in the methods today doesn't mean there won't be code there tomorrow. DODEFAULT in this case is very nearly a "zero cost" item to empty class methods. It's a "huge cost" to go back and retrofit them in if you ever put code in the class methods.