As VTK tries to be as retrocompatible as possible with extensive deprecation mechanism, VTK developers often struggle with the amount of work needed to cleanly deprecate protected members (non-virtual methods and variables). Indeed a protected members is perfectly accessible from a derived class, a…

Example, this should be avoided: vtkMyClass { protected: int myMember; } This should be prefered: vtkMyClass { public: vtkGetMacro(int, myMember); vtkSetMacro(int, myMember); private: int myMember; }

Without any negative feedback, I will add that recommendation in the guide.

https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10473

VTK

Member visibility when writing new VTK classes

Development

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled