I'm using the Hdf5DotNet interop assembly which is fantastic but it seems to
have an issue with the design of the H5ObjectsWithAttributes interface. The
H5A.create method requires an object of type H5ObjectWithAttributes.
Unfortunately H5DataTypeId does not derive from this interface so the
H5A.create method refuse to allow me to add attributes to a named data type.
Is there a reasonable workaround for this limitation?
BTW this also impacts my use of generics to create a HdfNamedObject<T> base
class constrained on T implementing H5ObjectWithAttributes as this again,
will not allow named DataTypes.
Keith, how are you? H5DataTypeId does not derive from H5ObjectWithAttributes
because most type handles do not refer to linked or committed HDF5
datatypes,
which are the only flavors of datatypes that can be decorated with
attributes.
My suggestion for a workaround would be to wrap and call H5Oopen http://www.hdfgroup.org/HDF5/doc/RM/RM_H5O.html#Object-Open
Which should return an H5ObjectWithAttributes. I'll add this to our issue
database, but I can't give you a date when we'll get around to addressing
this.
I'm using the Hdf5DotNet interop assembly which is fantastic but it seems to
have an issue with the design of the H5ObjectsWithAttributes interface. The
H5A.create method requires an object of type H5ObjectWithAttributes.
Unfortunately H5DataTypeId does not derive from this interface so the
H5A.create method refuse to allow me to add attributes to a named data type.
Is there a reasonable workaround for this limitation?
BTW this also impacts my use of generics to create a HdfNamedObject<T> base
class constrained on T implementing H5ObjectWithAttributes as this again,
will not allow named DataTypes.
