On Tue, Dec 2, 2014 at 1:03 PM, Nick Wellnhofer <[email protected]> wrote:
> I'm leaning towards combining novel methods with an exception for abstract > methods. What do you think? I think the difficulty of reasoning about how to document complex class hierarchies illustrates why many people consider implementation inheritance problematic. :D More practically... I'd suggest including complete documentation only when a DocuComment appears in the .cfh source file. For subroutines, that will generally mean only novel methods and inert functions, but it's conceievable that an inherited method could provide a DocuComment explaining something about its implementation. For public methods whose interfaces are established in superclasses, I suggest linking only. Marvin Humphrey
