|
|
|
Re: Model: abstract or interface? [message #1745898 is a reply to message #1745845] |
Wed, 19 October 2016 05:56 |
Ed Merks Messages: 33216 Registered: July 2009 |
Senior Member |
|
|
With with regard to 1., not all your classes are abstract so certainly not all your classes should be interfaces, multiple inheritance is not such a common pattern, and even when using multiple inheritance, you'll still generally want to reuse base class implementations as much as possible.
With regard to 2., you have a tool, you can write examples and see what they generate. I'm not here simple to describe hypothetical things that you might not be using in practice. You can answer such questions yourself. I suggest you create the classic diamond inheritance with A, B -> A, C -> A, D -> B, C and see how that's actually implemented by generated code.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03718 seconds