WIP: [Do not merge] Change the default char type to unsigned

[N-Dekker]

Just as an experiment!

Triggered by @blowekamp at #5450 (comment)

[N-Dekker]

itkHDF5ImageIOTest fails because of a bug (missing unsigned char support) in itkHDF5ImageIO.cxx, I think. Related to this code:

ITK/Modules/IO/HDF5/src/itkHDF5ImageIO.cxx

Lines 783 to 787 in 8de372e

	else if (metaDataType == H5::PredType::NATIVE_CHAR)
	{
	this->StoreMetaData<char>(&metaDict, localMetaDataName, name, metaDataDims[0]);
	}
	else if (metaDataType == H5::PredType::NATIVE_UCHAR)

So it treats NATIVE_CHAR different from NATIVE_UCHAR, even when the native (default) char is unsigned (equivalent to unsigned char).

However, I must say, I don't understand exactly what's going on there 🤷

[dzenanz]

Should this be closed or rebased, given that #5473 was merged?

[N-Dekker]

Should this be closed or rebased, given that #5473 was merged?

Thanks for asking, @dzenanz. It's still useful for me to keep this PR open for a little while, although it is never meant to be merged. I believe there are still a few small char/signed char issues in the source tree, which can be revealed by testing ITK with /J (MSVC) or -funsigned-char (GCC), as this PR does.

[dzenanz]

Should second and third commit be put into a separate PR, meant to be merged?

[N-Dekker]

Should second and third commit be put into a separate PR, meant to be merged?

• OK, for VTKPolyDataMeshIO: pull request BUG: VTKPolyDataMeshIO should use signed char for the SCHAR cases #5548

The HDF5ImageIO commit ("ENH: Support H5::PredType::NATIVE_SCHAR...") might be OK as well, but as I still see a failure of itkHDF5ImageIOTest, it may not be good enough yet 🤷