serializable data for ZFSerializable More...
Go to the source code of this file.
Classes | |
class | ZFSerializableData |
ZFSerializable's data container, see ZFSerializable. More... | |
Macros | |
#define | ZFSerializableKeyword_node |
keyword for ZFSerializable to hold a no name node, which means the data doesn't care about its class name | |
#define | ZFSerializableKeyword_prop |
keyword for ZFSerializable to hold attribute or property's name, see ZFSerializableData::propertyName | |
#define | ZFSerializableKeyword_value |
keyword for ZFSerializable to hold attribute or property's value, see ZFSerializableData::propertyValue | |
#define | ZFSerializableKeyword_category |
keyword for ZFSerializable's to hold category, see ZFSerializableData::category | |
#define | ZFSerializableKeyword_null |
used to declare a null object | |
Variables | |
zfbool | ZFSerializableDataResolveCheckEnable |
whether enable resolve check during serialization, true by default if not built as debug | |
serializable data for ZFSerializable
#define ZFSerializableKeyword_node |
keyword for ZFSerializable to hold a no name node, which means the data doesn't care about its class name
#define ZFSerializableKeyword_null |
used to declare a null object
serializing this would result a null with success state
the actual type for the null is determined by the owner
|
extern |
whether enable resolve check during serialization, true by default if not built as debug
resolve check may consume more CPU but useful during develop to find ill-formed serializable data
when on, check would be performed and an error output would be printed, further more, assert fail if ZFFramework was built as DEBUG mode
when off, no check would be performed, and all resolve related method would return false as resolved state
note, you must not change this config if some serialization logic is processing, usually, change it in app entry