>Jon,
>
>>Erm...thanks for the tip Mat but our problem is slightly more complicated than that. We wish to access the actual method CODE at runtime, as a developer aid to check DODEFAULTS exist where they should.
>
>If your methods don't require the use of DODEFAULT 99.99% of the time I'd say it's likely that your class designs need some serious work. Inheritance normally extends a class' functionality and if your subclasses/instances aren't using the functionality what is it doing there in the first place. Your programmers shouldn't really have much of a choice about whether or not they have dodefault in the code they write.

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.