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

Hi Ed,

> Quincey Koziol <koziol@xxxxxxxxxxxxx> writes:
> 
> > Hi Ed,
> >
> >> Elena Pourmal <epourmal@xxxxxxxxxxxxx> writes:
> >> 
> >> > Here is an example how to use H5Teeth_native instead of constructing 
> >> > memory type
> >> >
> >> > http://hdf.ncsa.uiuc.edu/training/other-ex5/h5nestc.c
> >> >
> >> 
> 
> ... snip ...
> 
> >     As part of the process of building the library, we generate information
> > about the compiler's padding for fields in compound types.  
> > H5Tget_native_type
> > uses that information to translate a non-native compound type into a native
> > compound type.
> >
> >     Quincey
> 
> If I understand you correctly, I need only call this function and all
> my inter-machine packing problems go away.

    Yes, probably.

> Thanks for providing H5Tget_native_type. It's very convenient!

    You're welcome! :-)

        Quincey