[Insight-developers] GDCM 2.x [was CMake Flag to make itk::Image behave like itk::OrientedImage]

[Mathieu Malaterre]

I am using partial template specialization (not the one with Brad's
trick to get function (template) overloading at function level). I
think it gave an ICE, or simply a compiler error. I do not have VS6 so
I cannot double check that.

On Mon, Sep 15, 2008 at 5:49 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> Unfortunately, Mathieu says that the new GDCM will not compile under
> VS6. I believe we still have customers that use VS6. There have been
> recent questions regarding VS6 on the users list.
>
> Mathieu,
>
> What sort of errors do you get with a VS6 compiler?
>
> Bill
>
> On Mon, Sep 15, 2008 at 11:44 AM, Stephen Aylward
> <Stephen.Aylward at kitware.com> wrote:
>> On Mon, Sep 15, 2008 at 11:06 AM, Karthik Krishnan
>> <karthik.krishnan at kitware.com> wrote:
>>> If I am not mistaken, I don't think the Backward compatibility policy
>>> applies to any of the third party software in Insight/Utilities.
>>
>> Actually, we consider all API's published by ITK to be "public APIs of
>> ITK."    We debated how this applied to Utilities many years ago, and
>> the final agreement was that there should be every effort to maintain
>> the quality and backward-compatibility of the code and APIs in
>> Utilities as much as possible.   You can probably search the email
>> archives and find that discussion.
>>
>>>
>>>> Here is what I am planning to do : add support for the new GDCM 2.x
>>>> architecture via the use of ITK_USE_SYSTEM_GDCM. A compiler #ifdef
>>>> will determine the MAJOR version of GDCM and if GDCM 2.x is found, a
>>>> different implementation will be used,
>>>
>>> Out of curiosity, is that more of a pain than upgrading the GDCM in
>>> ITK to 2.0.x ? If so, I wonder what the developers think about
>>> upgrading the GDCM in ITK, since DICOM handling is pretty fundamental
>>> for ITK.
>>
>> I think we should upgrade.   If the API breaks backward compatibility,
>> then we need to acknowledge it, warn users, and try to mitigate the
>> negative effects.
>>
>> The rough part happens is when someone has been compiling with
>> use-system-gdcm and that system gdcm is version X and now itk's
>> internal gdcm is moved to version X+1.    We may need to make changes
>> in ITK to allow either version to be used externally as well as
>> version X+1 internally.  Yuck...but an improved dicom reader is worth
>> it.
>>
>> Stephen
>>
>>>
>>> Thanks
>>> --
>>> Karthik Krishnan
>>> R&D Engineer,
>>> Kitware Inc.
>>> Ph: 518 371 3971 x119
>>> Fax: 518 371 3971
>>> _______________________________________________
>>> Insight-developers mailing list
>>> Insight-developers at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-developers
>>>
>>
>>
>>
>> --
>> Stephen R. Aylward, Ph.D.
>> Chief Medical Scientist
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (518) 371-3971 x300
>> _______________________________________________
>> Insight-developers mailing list
>> Insight-developers at itk.org
>> http://www.itk.org/mailman/listinfo/insight-developers
>>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
>



-- 
Mathieu