Re: The (ab) use of iObject
Mat Sutcliffe <[email protected]>
| Newsgroups | gmane.comp.graphics.crystalspace.devel |
|---|---|
| Message-ID | <CACE5BzLy3UaVE5E8UhdKWEcqkRLGTYxGeT9DL-GZhnn3B6M82g@mail.gmail.com> |
It's not about inheritance. The parent of an iObject instance is another iObject instance. The parent and child object are each aware of each other, as they store pointers to each other. An iObject instance can have zero or more children and zero or one parent. So you get a heterogeneous tree of instances of classes that all implement iObject. FWIW I agree it sounds like a good idea to use a different approach for telling iSaverFile which objects to save. On 5 September 2012 22:36, Scott Johnson <[email protected]> wrote: > Is this something that is required for another language? I was under > the impression that in C++ you _could_ have multiple inheritance (even > though it's probably not recommended). Is this something that changed > now in C++11? > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Crystal-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-develop