View previous topic :: View next topic |
Author |
Message |
csauls
Joined: 27 Mar 2004 Posts: 278
|
Posted: Mon Apr 26, 2004 12:34 pm Post subject: MI |
|
|
Well as I'd suspected Steve uses Multiple Inheritance in a few places... see file 'ogrenew/Docs/api/html/classOgre_1_1EventProcessor.html' for an example. So how shall we deal with this? One option is to use interfaces, but unless mixins happen soon, that would mean a lot of extra coding for all the interface implementors. _________________ Chris Nicholson-Sauls |
|
Back to top |
|
|
larsivi Site Admin
Joined: 27 Mar 2004 Posts: 453 Location: Trondheim, Norway
|
Posted: Mon Apr 26, 2004 3:30 pm Post subject: Re: MI |
|
|
csauls wrote: | Well as I'd suspected Steve uses Multiple Inheritance in a few places... see file 'ogrenew/Docs/api/html/classOgre_1_1EventProcessor.html' for an example. So how shall we deal with this? One option is to use interfaces, but unless mixins happen soon, that would mean a lot of extra coding for all the interface implementors. |
Ok, I had to look at the header file to see what you meant. Might be a problem. We probably need to look closer at he event system as a whole. There might be better solutions. |
|
Back to top |
|
|
csauls
Joined: 27 Mar 2004 Posts: 278
|
Posted: Mon Apr 26, 2004 3:41 pm Post subject: |
|
|
*nods* Might go into realms like those being explored by the DWT team. Or do something wild with member templates. Or both. I figure we could always have a stand-alone hierarchy of event system objects, and have them tie into the main framework via delegates or the like. All just hypotheses right now. _________________ Chris Nicholson-Sauls |
|
Back to top |
|
|
larsivi Site Admin
Joined: 27 Mar 2004 Posts: 453 Location: Trondheim, Norway
|
Posted: Tue Apr 27, 2004 2:17 am Post subject: |
|
|
In many places it might be relevant to look into has-a relations instead of is-a relations. |
|
Back to top |
|
|
csauls
Joined: 27 Mar 2004 Posts: 278
|
Posted: Tue Apr 27, 2004 12:17 pm Post subject: |
|
|
The has-a approach really probably is best... we'll just have to run with it and see what it ends up requiring of us. Might end up writing callback hooks for objects and their 'owners' to work together, but that's not too bad. _________________ Chris Nicholson-Sauls |
|
Back to top |
|
|
|