forked from gonum/hdf5
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This patch features an improvement of the HDF5 PacketTable Append method. This was necessary, because the old version did not support the append of struct containing nested structs and/or slices/arrays. To sum it up: - Any data of any Compound Datatype can be written to a PacketTable now. - This is achieved by allocating memory that contains the necessary data. - The whole code is simpler than the doubled code that excisted before. - The Append() method now supports proper appending of slices, which are not appended in a append-per-member manner, but rather as several objects to append that are consecutively in memory. This is more aligned with the offical way-of-doing. What needs to be improved? - The append of pointers still follows the old notion that we derefence the pointer and write the value directly. To support H5T_STD_REF_OBJ, further, significant changes have to be done to the whole code base. - The read functionality has to be revised, as it seems to not work when strings are part of compound datatypes. Manual testing has shown that they are written properly, the test cases still would fail, because of the mentioned call to read.
- Loading branch information
1 parent
ca618cf
commit 229165f
Showing
4 changed files
with
144 additions
and
147 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters