On 12/2/05, Dave Ross <[EMAIL PROTECTED]> wrote: > wow... very interesting. I think basically this boils down to the fact > that we expect concrete classes to have their own constructor (not > sure where that sits in terms of "best practice").
Hmm, I'm not sure either. I suspect that "best practice" leans toward always providing a constructor, even if all it does is call super.init(argumentCollection=arguments). > If anyone on the list has comments about this, I'd love to hear them. > In earlier versions of ColdSpring, we called init on any CFC without > even checking, but obviously that pissed a few people off. Now we > check to see if it's there before calling it, but we're not checking > in parent classes (so Adam's inherited init() would never get called). > Pretty easy fix, but I'd still like to hear others thoughts. How do you do the test such that it fails? structKeyExists(obj,"init") ought to return YES for inherited methods... yes? -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
