GitLab

It make senses since it allows for providing different iteration orders
for new array types.

No need to use allocators, instead we simply let the array implement
AllocateTuples/ReallocateTuples.

Converting some pure virtual methods to non-pure viz.
RemoveLastTuple/RemoveFirstTuple now simply call RemoveTuple with
appropriate index.

The default NULL value for UpdateExtent(const int extent[6]) was a typo.

Reworked code to just not use comma operator,
which is rarely used and poorly understood.

Changed some parameters to be by reference,
instead of by value, including some public API.

This is a general framework to interpolate attributes from a data source,
using the input as the set of interpolation points. It requires
specifying an interpolation kernel (several of which have been
created), as well as a locator for fast spatial searching. Although
similar in concept to vtkProbeFilter, it does not interpolate
using a cells interpolation basis, rather it uses a local evaluation
of the specified kernel, applied to the local points (neighborhood)
around each interpolation point, to compute the interpolated data values.
The algorithm is threaded with vtkSMPTools.

Docs say it should be 100 by default, so I just used that.

This removes the Kaapi and Simple backends, as they are no longer supported.
OpenMP and TBB are the supported backends.

Defines a macro "VTK_SMP_<Backend-Name>" and macro VTK_SMP_BACKEND which
expands to a string containing the back-end name.

When C++ args with default parameter values are wrapped, those same
parameters should have the same default values in Python.

The call to ResizeTableForSpecialColors resizes the Table array,
invalidating the pointers 'table' and 'tptr', leading to crashes:

https://open.cdash.org/testDetails.php?test=414805862&build=4211477

- warning about not rethrowing
- added extra parens
- warning about iterator misuse
- unused variable

Warning about deprecated methods coming from deprecated
methods is unnecessary. Disabled.

Deprecated methods calling deprecated methods was causing
warnings. Disabled until we remove the deprecated methods.

The way algorithms were updated (made to execute) with
request meta-data (such as update extent) was very error
prone and counter-intuitive. Added new methods to make
updating with meta-data easier. I also deprecated a number
of methods to set request meta-data. This will encourage
developers to migrate to the new API which is less error-
prone.

Find/replace of:

with C++ counterparts.  Changed only vtk*.cxx files.
Didn’t touch .h or .c or any 3rd party.

If the number of colors is zero, then we force the out-of-range colors
to be used because there are no lookup table colors to use instead.

This make it easier to build editions which just include DataModel and
dependencies. DataModel module gets included in a "StandAlone" build of
VTK since several other modules in the StandAlone group depend on
DataModel. However, if the edition only has DataModel (and none of the
other modules that depend on it), it doesn't get enabled by default.
Given our definition of "StandAlone" module, DataModule should indeed be
a part of it. Hence, adding it to that group.

Mostly of the form:

A || (!A && B)

to simply:

A || B

Warned by cppcheck

Valgrind detected a memory leak in
TestSortFieldData. vtkSortFieldData::Sort returns the array idx. It is
never freed.