Given 3 cfcs, abstractBase.cfc, abstractSpecific.cfc, and childSpecific.cfc. childSpecific extends abstractSpecific, which extends abstractBase. When instantiated, child's init() calls super.init() of abstractSpecific, which calls super.init() of abstractBase. However, this is only seeming to work if abstractSpecific is not an abstract component. Am I wrong in believing that an abstract component's init() should be able to call the super.init() of it's parent abstract component? There is a cf blog post from 2018 that shows that I can... https://coldfusion.adobe.com/2018/07/oop-and-coldfusion/#:~:text=Abstract%20Component%20%26%20Methods%20have%20been,both%20abstract%20and%20concrete%20methods.

Instead of describing the code, actually giving us a gist with an example of what yer doing would have been really helpful here. Because as it stands, now if we wanna investigate, we have to mess around duplicating the work that you've already done.

AbstractBase.cfc

/**

* @output false **/ abstract component{ /** * @output false **/ public AbstractBase function init(){ return this; } } AbstractSpecific.cfc /** * @output false * @extends AbstractBase **/ abstract component{ /** * @output false **/ public AbstractSpecific function init(){ Super.init(); return this; } } ChildSpecific.cfc /** * @output false * @extends AbstractSpecific **/ component{ /** * @output false **/ public ChildSpecific function init(){ Super.init(); return this; } }

that wasn't a gist, was it. It was just a whole sea of code inline, not even with formatting 😐 This is a gist: https://gist.github.com/adamcameron/e4bd8592a047def27a4455627704d248 (and it works exactly how I'd expect, guessing what you were meaning) But anyway... lemme look @ this code of yours

well, that's interesting, first time in over a decade i've had a problem with annotations

Just gonna try your code on Lucee and see what it does

i've used them for everything, accessors on properties, component settings, as much as I can

No comment. 😉

very.

Yeah and Lucee works fine if you use code rather than comments

only seems to be a problem for me with abstracts

oh

I'm on a roll finding obscure bugs this year

I'll add another vote that comments should not alter how code runs. Comments are, erm, comments (the annotation is inside a comments block). They can be useful for generating documentation. I'm sure it looked cool at the time Adobe decided to add it, but means that we have 3 ways for everything (cftag attributes, cfscript attributes and cfscript comment annotations). Having said that, as it is a thing, it should work :)

Yep it's def an approach to writing code I would actively dissuade in an environment when I make the calls on such things. I think doing stuff in comments when it can be done with code is... weird. Ah well.