Update handling of mxOPAQUE_CLASS objects and Subsystem in MAT_v5.jl #205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spinoff from #23 to read the undocumented datatype
mxOPAQUE_CLASS
. Part of a series of changes to read and write these types across formatsv5
andv7.3
.Some context :
uint8
array. However, this looks like another MAT-file that needs to be converted and read into. This needs to parsed before reading any variables in file.Edit:
Added a new file "MAT_subsys.jl" which contains methods for caching, parsing, and retrieving subsystem data to be assigned to an object. With this it should successfully load classdef objects. Additional context regarding how subsystem data is organized below:
uint32
integers even though its written in asuint8
-- Block 1 is a version indicator and some offset values
-- Block 2 is a list of class and property names as uint8 integers (null terminated)
-- Block 3 is a list of class IDs
-- Blocks 4 and 6 contain some metadata about how linking property names and property values
-- Block 5 is a list of object ID metadata
-- Block 7 is a list of dynamic properties attached to the object
-- Blocks 8 and 9 are unknown