Persistent objects (class 0x5af03000)¶
SS_MAGIC_ss
is a collection of related C preprocessor symbols defined in ssobj.h.
Synopsis:
SS_MAGIC_ss_persobj_t
: just the class part
SS_MAGIC_ss_scopeobj_t
:
SS_MAGIC_ss_fieldobj_t
:
SS_MAGIC_ss_roleobj_t
:
SS_MAGIC_ss_basisobj_t
:
SS_MAGIC_ss_algebraicobj_t
:
SS_MAGIC_ss_evaluationobj_t
:
SS_MAGIC_ss_relrepobj_t
:
SS_MAGIC_ss_quantityobj_t
:
SS_MAGIC_ss_unitobj_t
:
SS_MAGIC_ss_catobj_t
:
SS_MAGIC_ss_collectionobj_t
:
SS_MAGIC_ss_setobj_t
:
SS_MAGIC_ss_relobj_t
:
SS_MAGIC_ss_fieldtmplobj_t
:
SS_MAGIC_ss_topsobj_t
:
SS_MAGIC_ss_blobobj_t
:
SS_MAGIC_ss_indexspecobj_t
:
SS_MAGIC_ss_fileobj_t
:
SS_MAGIC_ss_attrobj_t
:
Description: These are the magic numbers for the persistent objects themselves. They do not appear in the file but are
part of the transient information for an object. The order of things here is such that when synchronizing
a scope we minimize the number of forward references. That is, if objects of type A can point to objects of
type B
then we should synchronize type B
before type A.
Issues: These magic numbers must be in the same order as the persistent object link magic numbers (class 0x5af02000).
Also, they are mentioned in ss_pers_init
when constructing an HDF5 enumeration datatype.
If you add items here and they don’t show up as tables in the files then the SS_PERS_NCLASSES
constant defined
in sspers.h is probably not large enough.
See Also:
- Magic Numbers: Introduction for current chapter