[Octave-bug-tracker] [bug #39491] Change H5Giterate to H5Literate for HDF5 API

[Markus Appel]

Follow-up Comment #3, bug #39491 (project octave):

I replaced H5Giterate and on that occasion all functions deprecated in HDF API
v1.8, but am not finished testing and cannot continue in the next few weeks.
Sharing my progress in the attached diff on Andy's request (see
http://lists.gnu.org/archive/html/help-octave/2014-06/msg00155.html ).

Some notes:
* The HDF API may, depending on how it is compiled, support both v16 and v18
(see http://www.hdfgroup.org/HDF5/doc/RM/APICompatMacros.html ). Octave's
configure should use v18 over v16 whenever possible, even when it is not the
API default (which I think it didn't, not sure if my change worked yet)
* Building should work against all compatibility levels of the hdf API (hdf
configured with --with-default-api-version=[v18|v16] or with
--disable-deprecated-symbols), needs testing. I had problems building against
hdf libraries from a specific folder instead of the system-wide installed hdf
version, there was/might still be an issue with octave's
--with-hdf5-libdir=... and/or --with-hdf5-includedir=...
* struct fields were sorted alphabetically after loading from hdf, because api
v16 did not support tracking of creation order in the hdf file. It should work
now with v18, but forward/backward (and matlab?) compatibility needs more
testing (write with v16, read with v18, and vice versa).
* my code may still contain some debug output commands

(file #31540)
    _______________________________________________________

Additional Item Attachment:

File name: replace_deprecated_hdf.diff    Size:17 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39491>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/