[vtk-developers] Data structures in VTK (Implementation)

[David Gobbi]

Inheritance is an implementation detail now, but these containers
might possibly become part of the VTK interface sometime in the future.
So the containers should either be made into a heirarchy now, or at
the very least a heirarchy should be drawn out on paper to ensure that
the containers can be put into a heirarchy later.

 - David

On Thu, 21 Feb 2002, Lorensen, William E (CRD) wrote:

> Inheritance is an implementation detail. I'm suggesting we look at the api's.
>
>
> -----Original Message-----
> From: Andy Cedilnik [mailto:Andy.Cedilnik at kitware.com]
> Sent: Thursday, February 21, 2002 1:06 PM
> To: Miller, James V (CRD); Lorensen, William E (CRD);
> vtk-developers at public.kitware.com
> Subject: RE: [vtk-developers] Data structures in VTK (Implementation)
>
>
> At 12:53 PM 2/21/2002 -0500, Miller, James V (CRD) wrote:
> >STL actually uses very little inheritance.  Rather it relies on duplicating
> >a prescribed API.  For instance, "vector" and "list" do not share a base
> >class.  Instead they just provide similar API's.
>
> Which is strange in VTK. I would say it is better to define a clear
> hierarchy and stick to it. Use inheritance to avoid repetition and
> so on.
>
> Let us move away from STL.
>
>                          Andy
> _______________________________________________
> vtk-developers mailing list
> vtk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/vtk-developers
>