[Insight-developers] FW: VC++ memccpy warnings

[Lydia Ng]

Hi,

The following VC++ warnings (see below) are due to inclusion of
	#include <memory.h>
instead of
	#include <memory>

Are there any reasons why we can't uniformly use the second method?
This change should get rid of about 20+ warnings for VC++.

Files using the first method are:
\CODE\Common\itkImageConstIteratorWithIndex.h(20):#include <memory.h>
\CODE\Common\itkImageIteratorWithIndex.h(20):#include <memory.h>
\CODE\Common\itkScalarVector.h(21):#include <memory.h>

Cheers,
Lydia


------------------------------------------
Compiling...
itkMutualInformationMetricTest.cxx
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\memory.h(68) : warning
C4273: '_memccpy' : inconsistent dll linkage.  dllexport assumed.
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\memory.h(69) : warning
C4273: 'memchr' : inconsistent dll linkage.  dllexport assumed.
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\memory.h(70) : warning
C4273: '_memicmp' : inconsistent dll linkage.  dllexport assumed.
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\memory.h(85) : warning
C4273: 'memccpy' : inconsistent dll linkage.  dllexport assumed.
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\memory.h(86) : warning
C4273: 'memicmp' : inconsistent dll linkage.  dllexport assumed.
Linking...
   Creating library Release/itkMutualInformationMetricTest.lib and object
Release/itkMutualInformationMetricTest.exp