You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, CG_LONG_T can take on different values depend on whether it's on Windows. It's also incompatible with hssize_t because int64_t usually maps to long (e.g., on x86-64) instead of long long. (I'm not saying they should be compatible, but HDF5 changed how they handle these types in HDFGroup/hdf5#709 and I think that rationale also applies to CGNS.)
This is a minor headache for us in PETSc. Would you be amenable to a change similar to the HDF5 change above and adding PRIdCGSIZE (and others if someone wants them)?
Also, I'm assuming for now that 32-bit cgsize_t is important for some users. That makes it harder to package/distribute and requires libraries like ours to test both versions.
The text was updated successfully, but these errors were encountered:
HDF5 has the following definitions, which allow reading and formatting of type
hsize_t
.CGNS has
Unfortunately,
CG_LONG_T
can take on different values depend on whether it's on Windows. It's also incompatible withhssize_t
becauseint64_t
usually maps tolong
(e.g., on x86-64) instead oflong long
. (I'm not saying they should be compatible, but HDF5 changed how they handle these types in HDFGroup/hdf5#709 and I think that rationale also applies to CGNS.)This is a minor headache for us in PETSc. Would you be amenable to a change similar to the HDF5 change above and adding
PRIdCGSIZE
(and others if someone wants them)?Also, I'm assuming for now that 32-bit
cgsize_t
is important for some users. That makes it harder to package/distribute and requires libraries like ours to test both versions.The text was updated successfully, but these errors were encountered: