Skip to content

Conversation

N-Dekker
Copy link
Contributor

VTKPolyDataMeshIO originally casted the buffer to plain char * for component type SCHAR. However, SCHAR indicates that the component type is signed char.

Follow-up to pull request #5470 commit 70fbb2b "BUG: MINCImageIO should use signed char for CHAR and MI_TYPE_BYTE"

`VTKPolyDataMeshIO` originally casted the `buffer` to plain `char *` for
component type `SCHAR`. However, `SCHAR` indicates that the component type is
_signed_ char.

Follow-up to pull request InsightSoftwareConsortium#5470
commit 70fbb2b "BUG: MINCImageIO should use
`signed char` for `CHAR` and `MI_TYPE_BYTE`"
@github-actions github-actions bot added type:Bug Inconsistencies or issues which will cause an incorrect result under some or all circumstances area:IO Issues affecting the IO module labels Oct 10, 2025
@N-Dekker N-Dekker marked this pull request as ready for review October 13, 2025 10:46
@dzenanz
Copy link
Member

dzenanz commented Oct 13, 2025

/azp run ITK.Linux

@dzenanz
Copy link
Member

dzenanz commented Oct 13, 2025

/azp run ITK.Windows

@thewtex thewtex merged commit cb07a31 into InsightSoftwareConsortium:main Oct 13, 2025
17 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:IO Issues affecting the IO module type:Bug Inconsistencies or issues which will cause an incorrect result under some or all circumstances

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants