mercredi 20 janvier 2016

design for separated visualization from code of polymorph classes

I have some class hierarchy that is mainly a data model. eg:

class A; ///< abstract base class
class B: public A;
class C: public A;
class D: public A{
  QList<QSharedPointer<A>> m_a;
}

Now I want to write code to visualize a List<QSharedPointer<A>>. Visualization of the classes requires to distinguish of their real type. Obviously i do not want to add dependencies from my data to the visualization code.

Is there an elegant way to do so without conditionals based on dynamic casts?

Aucun commentaire:

Enregistrer un commentaire