H5Utils issues with long and long long types

[quantumsteve]

Expected behavior

H5Utils "does the right thing" when loading or writing either a std::vector<long> or std::vector<long long>

Actual behavior

On certain platforms, the user will encounter a linking error.

Platforms affected

On Windows long has the same length as int32_t, but it is a ​_different_​ type.
On Windows long long has the same length as int64_t, and it is the ​_same_​ type.
http://rextester.com/EEFS42414

On OS X & Linux long has the same length as int64_t, and is the ​_same_​ type.
On OS X & Linux long long has the same length as int64_t, but is a ​_different_​ type.
http://cpp.sh/7u2t

Related issue is nexus-code#428.

[quantumsteve]

HDF5 has H5T_NATIVE_LONG, H5T_NATIVE_ULONG, H5T_NATIVE_LLONG, H5T_NATIVE_ULLONG types, which (assuming the NeXus format allows them) may be useful. Otherwise, we may need our own logic to steer long on Win32 to int32_t and long long on Linux to int64_t.

[peterfpeterson]

The good news is we don't support win32.

[quantumsteve]

By Win32 I mean 64-bit Windows, which we do support. WIN32 is a macro often used to determine a Windows machine and defined in both 32 and 64-bit builds..

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.