[Insight-developers] [Insight-users] ITK & VISUAL STUDIO 6.0 : How many users ?

[Luis Ibanez]

Hi Bill,


Actually, I'll take back the suggestion for committing
a file to test partial specialization.


I just remember that yesterday Brad King pointed me to a
try compile in VXL that checks for partial specialization.


It is in:

    Insight/Utilities/vxl/config/cmake/config

            vxl_platform_tests.cxx


Lines 140-170

---------------------------------------------------
#ifdef VCL_CAN_DO_PARTIAL_SPECIALIZATION

template <class T>
class victor
{
   T data[256];
  public:
   victor() {}
   T &operator[](unsigned i) { return data[i]; }
};

template <class T>
class victor<T *>
{
   T *data[256];
  public:
   T * &operator[](unsigned i) { return data[i]; }
   void slarf() { data[0] += (data[2] - data[1]); }
};

template <class A, class R>
struct foo {
   typedef A a;
   typedef R r;
};

template <class T> struct foo<T *, T *> { void bar() {} };
template <class T> struct foo<int *, T> { void baz() {} };

int main() { return 0; }
#endif // VCL_CAN_DO_PARTIAL_SPECIALIZATION
---------------------------------------------------


and it is run by the CMakeLists.txt file in the same
directory.


So we just need to check for the symbol
"VCL_CAN_DO_PARTIAL_SPECIALIZATION" on every platform
that we want to evaluate.


That is, we should be able to do this with today's builds.


     Luis



-------------------
Luis Ibanez wrote:
> 
> 
> Hi Bill,
> 
> 
> 
> A) Is VS 6.0 the only one that doesn't
>    support partial specialization ?
> 
> 
> My recollection is that at some point it was recommended
> that if we dropped support for Visual Studio 6.0, we should
> do it as well for VS 7.0 since it also have some weaknesses
> on support for templated code.
> 
>        I humbly suggest a one-day experiment:
> 
> Let's commit to CVS an isolated small file that exercise
> template partial specialization, and tomorrow we will have
> an answer for the range of platforms that we support.
> 
> Yes, it will cost a day of red Dashboard,...  :-/
> 
> but if nothing depends on this file, then we will still get
> all the test running for the normal submissions.
> 
> A less exciting option is to pass around a minimal example,
> and we compile in our local machines, then report back to
> the Wiki page:
> http://www.itk.org/Wiki/Proposals:Dropping_Support_for_Visual_Studio_6.0
> 
> 
> 
> B) Does VTK supports VS60 ?
> 
>    Yes, VTK is build Nightly on VS60 on Dash13.kitware.
> 
>    I see the point that it may be good to have a similar
>    set of platforms for ITK and VTK.
> 
> 
>    However,
>    VTK's uses of generic programming is a lot lighther
>    than ITK's, and therefor, supporting VS60 may not
>    represent in VTK the same level of restriction that it
>    is in ITK.
> 
> 
> 
>    Luis
> 
> 
> 
> ---------------------
> Bill Lorensen wrote:
> 
>> Luis,
>>
>> Are we positive that VS6 is the only ITK-supported compiler that does
>> not support partial specialization?
>>
>> Also, does VTK support the VS6 compiler? I think it does.
>>
>> Bill
>>
>> On Tue, May 13, 2008 at 2:14 PM, Luis Ibanez <luis.ibanez at kitware.com> 
>> wrote:
>>
>>> It has been pointed out in the following bug report that
>>> we should consider dropping support for Visual Studio 6.0:
>>>
>>>
>>>     http://www.itk.org/Bug/view.php?id=7006
>>>
>>>
>>>
>>> We would like to hear from users on how important they
>>> consider the support for Visual Studio 6.0 to be in ITK.
>>>
>>> In other words:
>>>
>>>
>>>        How many users are building ITK
>>>        applications with Visual Studio 6.0  ?
>>>
>>> and
>>>
>>>        How critical is this support for them ?
>>>
>>>
>>>
>>> The suggestion in the bug report is to drop the support
>>> for Visual Studio 6.0, in order to be able to introduce
>>> partial specialization in the toolkit.
>>>
>>>
>>>
>>>  We will appreciate your feedback,
>>>
>>>
>>>    Thanks
>>>
>>>
>>>       Luis
>>> _______________________________________________
>>> Insight-users mailing list
>>> Insight-users at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-users
>>>
>>
>>
>