[Insight-developers] Examples/Morphogenesis OperatingRoom

[Bill Hoffman]

That may be, but I don't think we want to encourage that.

vcl_cmath.h ->  math.h
vcl_cstdlib.h -> stdlib.h
vcl_cstdio.h -> stdio.h

I think i would rather depend on the system headers when possible.

-Bill


At 10:23 AM 10/16/2001 -0400, Lorensen, William E (CRD) wrote:
>Actually, most vcl_ includes are in Unsupported or Examples.
>
>./Examples/OperatingRoom/liC_Arm3D.cxx:#include <vcl_cmath.h>
>./Examples/OperatingRoom/liCone3D.cxx:#include <vcl_cmath.h>
>./Examples/OperatingRoom/liCylinder3D.cxx:#include <vcl_cmath.h>
>./Examples/OperatingRoom/liFluoroscopyUnitView.cxx:#include <vcl_cmath.h>
>./Unsupported/MetaImage/MetaFileLib.cxx:#include <vcl_cstdlib.h>
>./Unsupported/MetaImage/MetaFileLib.cxx:#include <vcl_cstdio.h>
>./Unsupported/MetaImage/MetaFileLib.cxx:#include <vcl_cstring.h>
>./Unsupported/MetaImage/MetaImageLib.cxx:#include <vcl_cstdlib.h>
>./Unsupported/MetaImage/MetaImageLib.cxx:#include <vcl_cstdio.h>
>./Unsupported/MetaImage/MetaImageLib.cxx:#include <vcl_cstring.h>
>./Unsupported/MetaImage/MetaImageLib.cxx:#include <vcl_cmath.h>
>./Unsupported/MetaImage/MetaUtils.cxx:#include <vcl_cstdlib.h>
>./Unsupported/MetaImage/MetaUtils.cxx:#include <vcl_cstdio.h>
>./Unsupported/MetaImage/MetaUtils.cxx:#include <vcl_cstring.h>
>./Unsupported/FltkImageViewer/fltkGlWindowInteractive.cxx:#include <vcl_cmath.h>
>./Unsupported/FltkImageViewer/fltkWindowInteractive.cxx:#include <vcl_cmath.h>
>./Unsupported/FltkImageViewer/fltkImage2DViewerWindow.cxx:#include <vcl_cmath.h>
>./Code/IO/itkVOLImageIO.h:#include "vcl/vcl_cstdio.h"
>./Unsupported/MetaImage/MetaFileLib.h:#include <vcl_cstdio.h>
>./Unsupported/MetaImage/IView/GLSliceView.h:#include <vcl_cmath.h>
>
>-----Original Message-----
>From: Bill Hoffman [mailto:bill.hoffman@kitware.com]
>Sent: Tuesday, October 16, 2001 10:08 AM
>To: Lorensen, William E (CRD); 'Luis Ibanez'
>Cc: insight-developers@public.kitware.com
>Subject: Re: [Insight-developers] Examples/Morphogenesis OperatingRoom
>
>
>Do we really want to use vcl_ in itk code?  Better might be to just include
>the c version of the files.  cstring --> string.h  ctypes -> types.h both are
>valid for ansi c++, but the SGI does not support the c* versions, so they
>should be avoided.   I don't think we want to get into to much vcl code directly
>in Insight.
>
>-Bill
>
>
>At 08:42 AM 10/16/2001 -0400, Lorensen, William E (CRD) wrote:
>>Subject example needs to include vcl_ include files for portability. Also, MRIBiasCorrection has
>many
>>compile errors on the sgi. Some of these error have been there for several dashboards.
>>
>>Bill
>>
>>_______________________________________________
>>Insight-developers mailing list
>>Insight-developers@public.kitware.com
>>http://public.kitware.com/mailman/listinfo/insight-developers 
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers