[vtk-developers] Data structures in VTK

[Lorensen, William E (CRD)]

Certainly we should look at STL. For example, I believe that CMake uses some stl. Insight (the NLM
toolkit) uses it heavily, but does have some portability problems.

For example, SGI does not ship an STL that is thread safe. (OK the story is longer than that).
For Insight, we have to build a development from SGI.

It takes a long time to get these sorts of things right. I would discourage any more STL like classes
in vtk.

Bill

-----Original Message-----
From: Prabhu Ramachandran [mailto:prabhu at aero.iitm.ernet.in]
Sent: Friday, December 28, 2001 1:27 PM
To: vtk-developers at public.kitware.com
Subject: Re: [vtk-developers] Data structures in VTK


>>>>> "SW" == Simon Warfield <warfield at bwh.harvard.edu> writes:

    SW> Does it really make sense to continue to avoid using STL ?

    SW> If vendor STLs are still too incompatible and not compliant
    SW> with the standard, then one option would be to use a drop in
    SW> replacement for vendor STL such as STLport
    SW> http://www.stlport.com/product.html

Yes, with more than 20 different compilers being supported it is
certainly unfair to say STLport is not cross platform.  However, maybe
the biggest worry is that by adding STLPort VTK will rope in another
dependency, which might not be desired.  So unless compilers ship with
a working STL it might not make sense to use STL.  That said, I find
it hard to believe that STL is not standard enough today.

prabhu
_______________________________________________
vtk-developers mailing list
vtk-developers at public.kitware.com
http://public.kitware.com/mailman/listinfo/vtk-developers