[coldspring-dev] No inherited init() methods

[Brian Kotek]

Chris, I think (could be wrong though) he means that if he wants his subclass CFC init() method to have proper API documentation, it would mean literally copying and pasting the cffunction and cfargument tags from the superclass and pasting them into the subclass, and then adding the call to super.init(argumentCollection=arguments) to the subclass. Any time he changes the superclass init(), he'll have to change all the subclass init() methods as well.

That seems to make sense to me, but on the other hand one could probably argue that if you have a subclass with no init(), not having the init() method show up in the API documentation for your subclass at all is just about as bad.

On 5/10/06, Chris Scott <[EMAIL PROTECTED]> wrote:

Coupling is evil.  If I have a subclass that doesn't need custom

initialization, why couple the signature of the init method to the

superclass's?

Um, I just have to fail to see how if you extend a class the inherited class is 'decoupled' from the super class, sorry...

Chris Scott

[EMAIL PROTECTED]

http://cdscott.blogspot.com/

http://www.coldspringframework.org/

On May 10, 2006, at 1:43 PM, Barney Boisvert wrote:

Coupling is evil.  If I have a subclass that doesn't need custom

initialization, why couple the signature of the init method to the

superclass's?