COMP: fixed llvm libc++ build error by removing invalid 'operator<<'

Change-Id: Ibc925dc9c71669249d257c93cc6b413704a84035
Fixed spelling in debug string.

Change-Id: Ie6663639195bcbafcfc00794f8ecb4d4f2a0cdbf
Prevent writing of non-0/1 values into bool

When running the test 'vtkCommonCoreTcl-TestSetGet',
clang's -fsanitize=bool complained:

runtime error: load of value 37, which is not a valid value for type 'bool'

The code called resize() on an stl vector which ended up using the default
constructor (which didn't initialize any ivars) and then subsequent new items
(I think) were copied from this one prototype by
IVFDataSetInfo::IVFDataSetInfo(const IVFDataSetInfo &ivfci)
which then copied the randomly-initialized bool into another bool,
and thus the error.  Fixed by zeroing everything in the default ctor.

Change-Id: Icd1a8c1b6a6eb84b525048b0177910f2a7d2f855
Fixing tolerance issue for test.

Change-Id: I4738aa963e558cf5ec75e048541f9c16d4ad58a7
Merge topic 'TestGradientAndVorticity' into master

cc318c0a Fixing tolerance issue for test.
Fix valgrind error in vtkBlueObeliskDataParser

This fixes "Conditional jump or move depends on uninitialised
value" error issued by valgrind. The atof() call resulted in the
valgrind error when the data is non-numeric. This fixes the error
by using std::stringstream to parse the data instead of atof().

This should fix most of the valgrind errors in the chemistry tests.

Change-Id: I9dfbcf74524d8862d09ded5ba1a85d5dc9d160b3
Merge topic 'libc++-fixes' into master

c50bcb3b Fixed spelling in debug string.
6e704e64 COMP: fixed llvm libc++ build error by removing invalid 'operator<<'
Merge topic 'fix-blue-obelisk-data-parser-valgrind-error' into master

6987a855 Fix valgrind error in vtkBlueObeliskDataParser
Merge topic 'sanitize-bool' into master

8e7375d3 Prevent writing of non-0/1 values into bool