>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.

I guess our design strategies differ here. The sort of hook I normally build into my classes is used ONLY for instance code, and this does mean that there will never be class code in there. If I find myself wanting to add class code here, it means I implemented the design wrong, and I need to rethin where to put the code... there is always a more appropriate place.