[vtk-developers] Adding support for a macro in wrapper
david.gobbi at gmail.com
Wed Mar 11 15:21:04 EDT 2015
The wrappers understand but ignore the "using" directive. So, yeah, wrapper
changes would be needed to support it. For example, I have wrapper code on
github that pulls in the header files for all the superclasses so that it
used methods from the superclass namespace.
What was your original macro? In general, the wrappers should be able to
handle most macros without any problems.
On Wed, Mar 11, 2015 at 12:51 PM, David Lonie <david.lonie at kitware.com>
> On Wed, Mar 11, 2015 at 2:49 PM, Ben Boeckel <ben.boeckel at kitware.com>
>> On Wed, Mar 11, 2015 at 14:27:43 -0400, David Lonie wrote:
>> > I'm in the process of deprecating
>> > virtual double* vtkProp::GetBounds();
>> > to favor a new signature
>> > virtual bool vtkProp::GetBounds(vtkViewport *, double);
>> > This is a major change that touches a lot of classes, plus it
>> introduces an
>> > overloaded signature to a virtual. This means that every subclass of
>> > vtkProp that implements GetBounds will need to define the deprecated
>> > signature so that it won't be hidden in legacy applications.
>> The solution is to do:
>> using SuperClass::GetBounds;
>> where GetBounds is reimplemented to "import" the subclass' overloads not
>> reimplemented here.
> D'oh! Forgot about that. Now let's see if the wrappers understand such
> things... ;)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtk-developers