Mi-La
Mi-La
The following example generates uncompilable code in C++, since the parameterized type is initialized with (non-constant) reference to string. ``` struct Parameterized(string param) { uint32 field; }; struct Test {...
Value evaluation doesn't work with data types and generated code can behave differently in each generator (e.g. how works data type overflow in C++, Java and Python). `ExpressionIntegerValue` shall know...
We should implement conversion from floating point types to string to enable it in the new [reflectable](103) interface, probably the support should be added in `StringConvertUtil` in zserio C++ runtime...
``` struct Test(uint32 p) { uint32 arr[]; p | p: uint32 value; }; ``` Offset expressions must point to a defined field. Note that the offset can be also array...
``` sql_table SomeTable { uint8 from; }; sql_database Db { SomeTable table; }; ``` SQLite keywords must be escaped properly!
Currently zserio automatically evaluates integral values and strings, and the result can be used directly by extensions. But boolean expressions doesn't evaluate it's values. This is necessary to support to...
When the ternary operators has constant condition (i.e. known in compile type), we should be able to evaluate value of the expression. Currently we only calculate upper/lower bounds of an...
Currently our zserio runtime library contains only `VERSION_STRING` constant. When it's imported in python as a zserio module, it would be nice to be able to get more "standardized" constants...
When an optional field depends on another optional field or on an optional parameter, zserio tries to check that the optional clause for both fields is the same. However we...
Currently in Java we do range checking immediately in field setters. However it can lead to exception for dependent fields. ``` struct Test { int8 numBits; bit bitField; // exception...