Wrapping: inheritance of method deletion
If a copy constructor is deleted, then the default copy constructor of a derived class is implicitly deleted since it cannot be generated by the compiler. The wrappers do not keep track of "inheritance of deletion", and can therefore generate code that attempts to call implicitly deleted methods.
An example of this can be seen if wrapping is applied to the GUISupportQt module. The wrapper for QVTKApplication will fail to compile because the superclass has a deleted copy constructor. Deletion of copy constructors in modern C++ code is a common thing, so this issue is likely to bite us in the future.
This defect is probably fixable by modifying the code in vtkParseMerge.c, which is where the wrappers keep track of inherited method attributes. Ideally this should be made to work even in cases where the superclass is not within the VTK code base.