|
From: Roger H. <rog...@mi...> - 2005-01-07 18:28:09
|
Ok, standing back for a moment I agree. I think all the static methods should stay in E3ClassTree whilst the non static ones should go into OpaqueTQ3Object. Of course E3ClassTree will have to be a friend of OpaqueTQ3Object. E3ClassTree become a stand alone class with no data in it. Its quite a small change but it should make things clearer. On Friday, January 7, 2005, at 06:17 pm, James W. Walker wrote: > Roger Holmes <rog...@mi...> wrote: > >> I have found a good solution, the real root class is now E3ClassTree, >> and >> OpaqueTQ3Object inherits from it (and currently adds no fields or >> methods). > > I don't get it. This would let OpaqueTQ3Object methods access members > of E3ClassTree, but not the other way around, which is what you want. > -- > James W. Walker, ScriptPerfection Enterprises, Inc. > <http://www.write-brain.com/> > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop > |