Closed NickFoubert closed 11 months ago
Thank you for the report! We will take care of this issue. A workaround could be to check the condition at an earlier point:
type Some_Message is
message
Flag : Boolean
then Spare_7_Bits
if Flag = True;
Spare_7_Bits : Spare_7_Bits;
First_Record : Some_Record;
end message;
Thanks for the quick response! My reproducer example wasn't quite the use case I need, in my case the Flag
would be to indicate whether another field was present, e.g.:
First_Record : Some_Record
then Second_Record
if Flag = True
then null
if Flag = False;
Second_Record : Some_Record;
for which I see there is issue #106 which would help if implemented (I don't think #95 quite gives me what I need). At the moment I'm trying to implement it the standard way, but even that isn't working at the moment due to this bug.
I don't have a good workaround for your use case in the current version (0.14.0). It appears that this bug was recently introduced. For the time being, you could try using the previous version (0.13.0).
This bug will be fixed in the next release (0.15.0).
When trying to generate the following:
RecordFlux crashes:
This seems to be the case anytime I try to add conditional transitions after a field that is a message type.
The code generates successfully if I omit the conditional transition to
null
on theFirst_Record
field.The code also generates successfully if
Some_Record
is changed to a scalar type and I keep the condition.