OMNeT++ 5.4 compatibility?

[m-wegner]

As OMNeT++ 5.4 is released, we are evaluating its compatibility with artery and our own code. Most notably the evaluation of expressions regarding SimTime in NED files seem to have changed (since OMNeT++ 5.3 already).

For example, this seems to be an issue in the CaService.ned, line 31f. which leads to an runtime error in OMNeT++ 5.4 stating "Cannot cast from type double to integer".

So, this issue is just a question, as you probably have a better insight into CaService, etc.: In general, what is the state of artery regarding OMNeT++ 5.4 compatibility? Thanks in advance!

[riebl]

@m-wegner Hi Martin,

I have tried Artery with OMNeT++ 5.4 before and haven't observed the described issue.
In general, Artery should already be compatible with OMNeT++ 5.4. However, there may be some regression bugs. I had no time to run extensive simulations with OMNeT++ 5.4 yet.

I am wondering why you are hit by this runtime error. Are you using the final OMNeT++ 5.4 or some release candidate?

[m-wegner]

Ok, once again thank you for the quick reply and your assessment!

We encountered this issue with one of our own services whose implementation follows quite closely the one of the CA service (and the NEDs are basically identical in the mentioned lines), and we concluded that this service just was executed first in line.
Maybe we jumped to this conclusion too quickly and this is really just an issue with our service. Will investigate further.

[m-wegner]

Ok, so we were able to narrow this down to an erroneous assignment within our service via par() which triggered the error for narrowing casts introduced in OMNeT++ 5.3. So, CaService and others should be fine as you said.

So, sorry for the noise and thanks for your time and help. Closing this issue then.