On Friday, 16 August 2013 at 17:08:36 UTC, Dicebot wrote:
That makes some sense indeed, all you need is to stop naming base class "_A" and give it a proper meaningful name that reflects its role in object model :)
Hey, it's shorthand :-)
From the conceptual purity point of view I still think that having bunch of template mixins instead of _A and just combining them into A or B is the proper way (inheritance should not be used as code reusage tool) - but D may not have powerful enough tools to makes this approach convenient, so resorting to old-school inheritance sounds pragmatical.
I'm happy to consider alternative ideas. I find that mixins are very useful like this but also find that stuff tends to gain complexity quite rapidly with their use.
You need to be aware though that I am personally an OOP hater and my advices should be reconsidered in with that in mind ;)
;-) Thanks for the thoughts and advice!
