[vtk-developers] Recent API changes
David Cole
david.cole at kitware.com
Thu Jan 12 16:22:29 EST 2006
There is little harm in keeping a single #include. However, if we must
always keep all #includes then they will always accumulate over time and
never get cleaned up even when they are no longer necessary or have been
replaced by something better. Projects that don't weed out the
unnecessary #includes compile slower and slower over time even while
computing power is still increasing.
I think most developers understand the risks of developing against the
HEAD of any CVS project. Folks that need stability should be snapped to
a branch point or using a code base that remains stable by some other
mechanism.
Just my opinion, of course... :-)
David
Utkarsh Ayachit wrote:
>Yes, may be you are correct. I didn't realize the impact of this change
>given that it's assumed that people include the headers for the classes
>they use in the .cxx file. However, if the consensus is otherwise, I
>have no qualms in adding the header file. I again, apologize for the break.
>
>Utkarsh.
>
>Lorensen, William E (GE, Research) wrote:
>
>
>>Usually there is little harm in keeping a #include. Trade this off with breaking code in the installed base.
>>
>>Thanks,
>>
>>Bill
>>
>>-----Original Message-----
>>From: vtk-developers-bounces+lorensen=crd.ge.com at vtk.org
>>[mailto:vtk-developers-bounces+lorensen=crd.ge.com at vtk.org]On Behalf Of
>>Wylie, Brian
>>Sent: Thursday, January 12, 2006 3:39 PM
>>To: Bill Lorensen; vtk-developers at vtk.org
>>Subject: RE: [vtk-developers] Recent API changes
>>
>>
>>Bill,
>>
>>Not sure about the exclusion of that specific header file. Utkarsh will
>>have to look into it. But I just wanted to give a general apology about
>>the break, Kitware is doing this work under the direction of Sandia to
>>support information visualization applications. Obviously we will try to
>>minimize the impact of the changes as much as we can.
>>
>>Best regards,
>>
>> Brian Wylie - Org 9227
>> Sandia National Laboratories
>> MS 0822 - Building 880/A1-J
>> (505)844-2238 FAX(505)845-0833
>> ____ _ __
>> / __ \____ _________ | | / (_)__ _ __
>> / /_/ / __ `/ ___/ __ `/ | / / / _ \ | /| / /
>> / ____/ /_/ / / / /_/ /| |/ / / __/ |/ |/ /
>> /_/ \__,_/_/ \__,_/ |___/_/\___/|__/|__/
>>
>> Unleash the Beast
>>
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: vtk-developers-bounces+bnwylie=sandia.gov at vtk.org
>>>[mailto:vtk-developers-bounces+bnwylie=sandia.gov at vtk.org] On
>>>Behalf Of Bill Lorensen
>>>Sent: Thursday, January 12, 2006 1:06 PM
>>>To: vtk-developers at vtk.org
>>>Subject: [vtk-developers] Recent API changes
>>>
>>>Folks,
>>>Last week, after a number of changes enhancing vtkDataArray,
>>>some of our itk code stopped compiling. I believe it is
>>>because itkDataArray.h is no longer being included by some
>>>other class.
>>>
>>>Was this an intentional change? What is the rationale? These
>>>sorts of API changes are troublesome.
>>>
>>>Bill
>>>
>>>_______________________________________________
>>>vtk-developers mailing list
>>>vtk-developers at vtk.org
>>>http://www.vtk.org/mailman/listinfo/vtk-developers
>>>
>>>
>>>
>>>
>>_______________________________________________
>>vtk-developers mailing list
>>vtk-developers at vtk.org
>>http://www.vtk.org/mailman/listinfo/vtk-developers
>>_______________________________________________
>>vtk-developers mailing list
>>vtk-developers at vtk.org
>>http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>>
>>
>
>_______________________________________________
>vtk-developers mailing list
>vtk-developers at vtk.org
>http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
>
More information about the vtk-developers
mailing list