Stephan Eberle

When designing feature models in a modular way it happens sooner or later that one has a feature model A the features of which imply or exclude certain features of...

Provide organize imports function for modules and build configurations

7

When having worked in an mbeddr project for a while a lot of stuff in gets accumulated in "imports" section of modules and "included modules" section of build configuration. It'd...

sizeof operator should return size_t

2

... but not uint32

Some C library headers such as [](http://pubs.opengroup.org/onlinepubs/9699919799/functions/stat.html) defines structs and functions that have the same name. Therefore, the typesystem rules in mbeddr should be tweaked a little bit to avoid...

E.g.,  Expected: an error on the second case clause that is a duplicate of the first one Actual: no error

E.g.,  Expected: no error Actual: * Error: type uint8 const volatile is not a subtype of int64 const volatile * Error: type int64 const volatile is not a subtype...

E.g.,  When compiling the generated code, the following compilation error is raised: Error[Pe852]: expression must be a pointer to a complete object type S:\code\mbeddr\solutions\com.itemis.smartmeter.ssec\source_gen\com\itemis\smartmeter\ssec\integrations\partial\sd24\FixedSizeDatagramPoolImpl.c 15 There should be a...

Example: Before:  After:  Expected: function name = delegatingJSONTreeInputHandler Actual: function name = input_handler

Examples:  ---------------------------------------------------------------------------------------------------------  ---------------------------------------------------------------------------------------------------------  ---------------------------------------------------------------------------------------------------------  --------------------------------------------------------------------------------------------------------- Expected: no warning Actual: Warning: Assigned variable is not used after this point.

To facilitate the navigation through mbeddr code using components/interfaces, the following features should be supported: 1. _Go to Implementations_ context menu entry for **required port operation invocations** and **interface operations**...