From: Ian S. <ian...@st...> - 2006-03-21 16:24:52
|
Amitha Perera wrote: > Ian Scott wrote: > >>I'd suggest pre-emptively getting rid of >>VC7.0: It was never widely used, and it lacked support for some of the >>more advanced C++ used by Boost, etc. > > > There is a current dashboard build for it, both for VXL and for our > internal libraries. Personally, I have no strong tie to it, but I > think that it's a recent enough compiler that I'd be more hesitant to > immediately deprecate it. Unlike VC6, I think VC70 (.Net 2002) is > still a vendor supported product. Deprecating VC7 is worth checking > again with vxl-users. Some of the more advanced C++ I use in our internal code does not compile under VC7.0. Some of this may migrate into contrib/mul at some point. The main reason to get rid of VC7.0 support is to allow us to focus on 7.1 support - which I personally expect to use for a long time. > Perhaps VC70 and gcc 3.0 and 3.1 could be part of a "proper" > deprecation process? Sounds like a good idea. > > > If no objections come up in our discussions here, I'll send a > warning/request to vxl-users tomorrow, notifying folks that > - VC6, gcc 3.0 and gcc 3.1 will not be supported in VXL 1.5 > - Suggest that we want to deprecate VC70 in VXL 1.5, and remove > support in VXL 1.6 I've got a draft email already waiting to go. I just wanted to float the VC7.0, etc suggestion here, before I sent it. If you would prefer to send the email, let me know. Ian. |