[Insight-developers] ITK4: OStringStream removal

[Bill Lorensen]

More info on the impact of removing OStringStream .

A google search shows the following large projects that have a least
one file that uses OStringStream:

Slicer3
Slicer4
orfeo-toolbox
IGSTK
mitk
Qmitk

The good news is that these customers can probably change
OStringStream to std::ostringstream and still build with ITK3.X.

The bad news is that they will get compilation errors (plus
potentially many more) when they upgrade to ITK4.

Bill

On Wed, Dec 29, 2010 at 3:55 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> My recent experiment that build Slicer4 against ITK4 illustrates the
> impact of API changes.
>
> Back in the day, we recommended that developers use itkOStringStream
> rather than std::ostringstream because the latter was not implemented
> by all of the itk platforms.
>
> Slicer4 uses itk::OStringStream in these files:
> ./Applications/CLI/BRAINSTools/BRAINSCommonLib/BRAINSMacro.h
> ./Applications/CLI/BRAINSTools/BRAINSCommonLib/GenericTransformImage.cxx
> ./Applications/CLI/BRAINSTools/BRAINSCommonLib/Test_FindCenterOfBrainFilter/ImageCompare.cxx
> ./Applications/CLI/DiffusionApplications/ResampleDTI/Testing/itkTestMainExtended.h
> ./Applications/CLI/MRIBiasFieldCorrection/ImageCompare.cxx
> ./Libs/vtkITK/itkEncodedTransformFileReader.cxx
> ./Libs/vtkITK/vtkITKArchetypeImageSeriesReader.cxx
> ./Modules/ChangeTracker/DiffeomorphicDemonsRegistration/ImageCompare.cxx
> ./Modules/Meshing/IO/itkMimxReadHistogramBinValuesFilter.txx
> ./Modules/Meshing/Mesh/itkMimxRebinHexahedronMeshTraitDataInPlaceFilter.txx
> ./Modules/Python/FilteredTractography/weave/scxx/scxx.h
>