hanhui03 / jstruct Goto Github PK

When using the JStruct tool, there will be a scene of multi-layer structure nesting.

for example:
struct json_attitude { float roll; float yaw; float pitch; void *json; };
In the user's perspective, we don't know when to use void *json member in structure.In what scenarios do we need to use it?

For example, data like this:
{"foo":1203456,"bar":100,"boo":true, "str":"hello!","arr":[1.0,1.1,1.2,1.3],"han":3,1414999961853027}
The result after deserialization is as follows:
foo : 1
bar : 0
boo : 1
str : hello!
arr[0] : 1.000000
arr[1] : 1.100000
arr[2] : 1.200000
arr[3 ]: 1.300000
han : 3.141500

The result of using method yyjson_get_real() to parse int type data is incorrect, and using method yyjson_get_int() instead has the correct result.

At present, there is a very common data structure as follows:

typedef struct
{
	union
	{
		unsigned short word;
		struct
		{
			unsigned code1		:3;
			unsigned code2		:5;
			unsigned code3		:2;
			unsigned code4		:6;
		}block;
	}order;
	...
}

In order to be compatible with a large number of early module codes, this is a necessary data structure, and this data structure will be transmitted with high-level programming languages.

After careful study, the conclusion is that under the current use scenario, the union cannot be serialized in general, but can only be parsed in a targeted way. In consideration of the universality of Jstruct, it is recommended to negotiate the special data types that may be encountered at present and in the future.