NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: compound types on different machines - is this expected?

Elena Pourmal <epourmal@xxxxxxxxxxxxx> writes:

> Here is an example how to use H5Tget_native instead of constructing memory 
> type
>
> http://hdf.ncsa.uiuc.edu/training/other-ex5/h5nestc.c
>

OK, this seems like magic!

I've changed by program to use the get_native_type function, and now
everything works perfectly. I've read the documentation for
H5Tget_native_type and it's really not clear to me how it manages to
deal with the padding of a struct.

Can someone explain what's going on? What does get_native_type do for
compound types?

Thanks,

Ed
-- 
Ed Hartnett  -- ed@xxxxxxxxxxxxxxxx