Can't you just define f5f_VARIABLE as uint64? The only place it's used
it's being converted to uint anyway (which seems slightly dubious in itself).
On 10 August 2017 at 09:03, Dan Kortschak <dan.kortsc...@adelaide.edu.au> wrote:
> I'm pretty sure this should never have worked, but it seemed to
> previously and now it doesn't.
> In the gonum/hdf5 package there is a var declared against an HDF5
> define like so, `var h5t_VARIABLE int64 = C.H5T_VARIABLE`.
> `H5T_VARIABLE` is defined in H5Tpublic.h as `#define
> H5T_VARIABLE ((size_t)(-1))`. Until this change, the code
> built, but now fails with
> # gonum.org/v1/hdf5
> ./h5t_shim.go:263: constant 18446744073709551615 overflows int64
> Is the appropriate way to deal with this to write a C function to
> return the value of the C H5T_VARIABLE define and assign that to
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.