Quote:Original post by DevFred
Why didn't you do this:

interface ISceneObjectabstract class SceneObject : ISceneObjectclass Renderable : SceneObjectclass PhysicsObject : SceneObjectclass AudioEmitter : SceneObject

Am I missing something?

Quote:Original post by Ahnfelt
Assuming we have explicit "virtual" and "override" for methods that can be / is being overridden or implemented, what if interfaces could define a body for methods declared "virtual"? (That is, methods that don't override other methods, but which can be overridden). That way you avoid the diamond problem, since you cannot override method bodies in sub-interfaces.

interface Vector2d {    virtual Float getMagnitude() {        return getX() + getY();    }    virtual Float getX();    virtual Float getY();}class Point implements Vector2d {    override Float getX() = x;    override Float getY() = y;    Float x;    Float y;}

It's still limited of course, since you can't override in interfaces - only in classes. This would be apparent if you tried to make a Vector3d interface inheriting from Vector2d, since it'd need another getMagnitude(). But would it cover your needs?

Quote:Original post by DvDmanDT

LANGUAGE	LOVES	HATESLolcode:	1	2

Quote:Original post by gharen2
While you couldn't override the method in another interface, it still raises the question: suppose you derive a class from two unrelated interfaces, both of which just happen to have an implementation declared for a getMagnitude method? Which implementation does the class use?

Quote:Original post by DevFred

Quote:Original post by DvDmanDT

LANGUAGE	LOVES	HATESLolcode:	1	2

ORLY? NONE CAN SRSLY HAS LOVE 4 LOLCODEZ!!!11

Quote:
What is your favorite programming language? Choose one, and only one. Also, give a reason why you like it.