[bug #68251] Load-Save support for MAT-file v7.3 (HDF5-based format)
foreverallama <[email protected]> Fri, 17 Apr 2026 07:58:08 -0400 (EDT)
| Newsgroups | gmane.comp.gnu.octave.bugs |
|---|---|
| Message-ID | <[email protected]> |
Please use the bug tracker to post updates to a bug report. The mailing list is intended as a read-only notification stream. Info posted to this mailing list address won't appear in the tracker database where it is most useful.
URL:
<https://savannah.gnu.org/bugs/?68251>
Summary: Load-Save support for MAT-file v7.3 (HDF5-based
format)
Group: GNU Octave
Submitter: foreverallama
Submitted: Fri 17 Apr 2026 11:58:04 AM UTC
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Feature Request
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Unlocked
Release: dev
Operating System: Any
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Fri 17 Apr 2026 11:58:04 AM UTC By: foreverallama <foreverallama>
Since this is something in the pipeline as well, I thought of working on it. I
see there's already a native HDF5 implementation under
"libinterp/corefcn/ls-hdf5.cc", so I'm proposing a new file
"libinterp/corefcn/ls-mat-hdf" to handle v7.3 MAT-files.
I'm starting with a patch to refactor the load path for v7.3 formats in
"load-save.cc" to check for the version in the MAT-file header. Reusing
"read_amt5_binary_file_header()" for this, where v7.3 files have "version==2".
I additionally added an early exit to "read_mat5_binary_file_header()" to
prevent subsystem from being read twice during load in v5/v7 versions (once to
retrieve file format, and once for load).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68251>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaeIgUAAKCRCqLAuaBUf3 TjTCAP0UiplQgW4eQgzkognH8BQ0jyjFZLUgobTacFQI6xaIfQEA2XRVsD7saTFx bVM/ILa+LJ1sHlfpahPQ5+++UG22TQQ= =3uXq -----END PGP SIGNATURE-----