[vtk-developers] VTK coding conventions clarification
Marcus D. Hanwell
marcus.hanwell at kitware.com
Tue Mar 18 11:30:36 EDT 2014
I agree with Rob, std::string is already included (and has been for
many years) as vtkStdString publicly inherits. It should just be added
as an exception.
On Tue, Mar 18, 2014 at 11:20 AM, Robert Maynard
<robert.maynard at kitware.com> wrote:
> I think we should just add std::string as an exception to rule #27.
> vtkStdString already publically inherits from std::string and so using
> that class doesn't reduce header bloat, but instead increases it.
> On Tue, Mar 18, 2014 at 11:09 AM, David Lonie <david.lonie at kitware.com> wrote:
>> Hi list,
>> Referring to the document here:
>> there are two conventions that appear to be in conflict:
>> 27. STL usage is disallowed in the Common modules' public API, and should
>> only be used in implementation files there. The other modules may use STL,
>> but should do so only when necessary if there is not an appropriate VTK
>> class. Care should be taken when using the STL in public API, especially in
>> the context of what can be wrapped.
>> Rationale: limits header inclusion bloat, wrappers are not capable of
>> handling many non-vtkObject derived classes.
More information about the vtk-developers