[vtk-developers] Started on VTK 4 compatibility removal

[Bill Lorensen]

ITK now requires a short xml description of API changes. These will
eventually be collected into a migration guide. There is info here:
http://www.itk.org/Wiki/ITK_Release_4/What_Developers_Must_Do_To_Contribute_to_the_Users_Migration_Guide
The migration policy and guide was created by Kitware as part of their ITKv4
contract.

I suggest that we do something similar in VTK. It is a small burden on the
developer that will make it easier on our customers. In ITK, we try to add a
migration document when me make the API change. This should save a lot of
effort later.

Bill

On Thu, May 5, 2011 at 11:27 AM, Sean McBride <sean at rogue-research.com>wrote:

> On Thu, 5 May 2011 10:45:14 -0400, Berk Geveci said:
>
> >We (ARB) discussed the possibility of getting rid of SetInput() and
> >creating a new function called SetInputData() to flag such issues at
> >compile time rather than runtime.
>
> 2¢: Flagging at runtime, say with an assert(), sounds fine to me.
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 sean at rogue-research.com
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec, Canada
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20110505/26efc2a4/attachment.html>