Tobias Reiher

I experience the same behavior. Is it a bug or a configuration problem?

It looks like you tried to use a message aggregate with a function call as an argument. When a message aggregate is used, the generator determines the size of the...

The issue is caused by the nested expression `Check_Tag (Msg.Inner_T)` (the field access `Msg.Inner_T` inside the function call `Check_Tag`). Nested expressions are not yet supported (cf. #1019).

It seems not to be possible to specify MQTT with ASN.1 in combination with ACN. ACN only supports the following encodings for integers: pos-int, twos-complement, BCD, ASCII.

> To avoid withing the whole `RFLX_Types` package I suggest to implement the operators in `RFLX.RFLX_Types.Operators` so only this package has to be used completely. This avoids all the visibility...

I think that would be a good thing. I don't see a good reason to allow the old/default operator behavior.

Private types are not yet supported in the code generator. During the implementation of the session support, there were doubts about the necessity/usefulness of private types. We have to decide...

I would keep this ticket as a reminder to either implement private types in the generator or remove private types from the language.

The actual problem is that `P` is unused in `M1`. The use of message types as field types is just some form of syntactic sugar. The message model does not...

I think the implicit checking of completeness and validity of a message should be preferred (O2). I'm not aware of a use case where the current behavior would be required...