[Insight-developers] ICE on vs6.0

[Bill Lorensen]

I rearranged includes in MeshSpatialObject and the ICE went away.

Bill

On Thu, Apr 1, 2010 at 3:36 PM, Luis Ibanez <luis.ibanez at kitware.com> wrote:
> Just to reinforce,
>
> Yes, I think that fixing the Windows 64 issues is a priority.
>
>          Today, we can't use images larger
>           than 2Gb under Windows 64 bits.
>
> --
>
> The only issue that has higher priority than this, is removing
> from ITK the code whose license is incompatible with BSD.
>
>
>     Luis
>
>
> ------------------------------------------------
> On Thu, Apr 1, 2010 at 1:32 PM, Bradley Lowekamp <blowekamp at mail.nih.gov> wrote:
>> Bill,
>> The future means before the 3.18 release. I believe it would be a mistake to
>> release this methods in it's current implementation, as it is just a
>> skeleton.
>>
>> The primary goal of this method was to aid in the support for 64-bit
>> windows. With the numerous types used with IO, and the sizes of images, this
>> function is needed to detect overflow errors to prevent crashes. Support for
>> "long long" was also added to  the numeric traits, so that we'd have numeric
>> traits for the Image::SizeType and size_t on windows 64.
>> It is my understanding that Luis believes adding support for win64 is a high
>> priority. As such I interpret that to mean that the 3.19 development effort
>> will have some focus on making this possible. This methods is a useful tool
>> for that work.
>> I assume that is just the result of some bug is VS6. Could be as simple to
>> fix as just changing the order of the header files in Math.h? Other files
>> seem to include itkConceptChecking with out issues.
>>
>> Brad
>>
>> On Apr 1, 2010, at 1:07 PM, Bill Lorensen wrote:
>>
>> If the future means itk 4.0, then can I remove it for now? I assume
>> that VS6 will not be supported in itk 4.0.
>>
>> Bill
>>
>