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

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?


Ed Hartnett  -- ed@xxxxxxxxxxxxxxxx