Miki

Currently, compiler warnings are not documented at all. All compiler warnings should be well documented with possibility of easy filtering to eliminate false positives.

GIVEN some user-specified std::string 'S', WHEN preparing some SQL Query 'Q' which gets concatenated with 'S', THEN before concatenating 'S' with 'Q', zSerio shall apply some SQL string sanitizer QLS...

Range check for dynamic field length

1

There is no range check for dynamic field length during runtime. Example: ``` struct Container { uint64 length; bit unsignedBitField; int signedBitField; }; ``` It would be nice to have...

Consider the following schema: ``` struct Test { varint32 id : id false (-1 > 1U) => true ```

If the variable array uses array size which can hold bigger value than the upper bound limit of `varsize` type, compiler could fire a warning that such schema does not...

Consider the following variable array: ``` struct VariableArray { uint64 numElements; uint8 uint8Array[numElements]; }; ``` Currently, there is no runtime check for number of elements in variable arrays in C++,...

Empty choices and unions generates unused member `objectChoice` in C++ and Java. Would be nice to improve it. Once fixed, don't forget to update filters for static analyzers (even in...

Python generates unused imports for empty choices: ``` enum uint16 TestEnum { DUMMY }; choice TestChoice(TestEnum type) on type { case DUMMY: ; }; ``` The previous example generates unused...

Currently, the maximum object size in bits is not defined. The maximum object size in bits is given by native type used to store the bit size: - 32-bit size_t...

Normally, `varsize` type should be mapped into native `size_t` type in C++. Unfortunately, this type has different size in 32-bit and 64-bit C++. But C++ generator needs to know bit...