[vtk-developers] Removing the vtkstd headers from VTK master - using STL directly

[Marcus D. Hanwell]

Yes, I thought I would need to do that, but not generate them at all
if remove legacy is on, and then perhaps remove them in for the 6.0
release. I can make that change, please let me know if you see any
other problems.

It isn't clear if they are part of our public API, but as we installed
them I guess they were.

Marcus

On Tue, Dec 13, 2011 at 11:55 AM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> I think you should keep the old headers around for backward
> compatibility. You could stick warning pragmas in the headers.
>
> On Tue, Dec 13, 2011 at 11:49 AM, Marcus D. Hanwell
> <marcus.hanwell at kitware.com> wrote:
>> Hi,
>>
>> I just pushed a topic to reviewtest that removes vtkstd from VTK. For
>> testing purposes I removed the generation of vtkstd altogether, but
>> that could be modified.
>>
>> http://reviewtest.source.kitware.com:81/#/t/31/
>>
>> This seems to compile for me, and was done largely using a Python
>> script and a little regex. Are there objections to me merging this
>> topic in? Should the vtkstd headers be generated for legacy purposes,
>> I know at least ParaView (which I can fix) is using vtkstd in some
>> places.
>>
>> I could also use some pointers from David Gobbi, as I suspect what I
>> did to the wrapper code was not quite right.
>>
>> Thanks,
>>
>> Marcus
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com