0000793: NED: local parameters cannot be used to initialize an inherited parameter

Notes
(0000951) andras (administrator) 2014-11-28 13:24 edited on: 2014-11-28 13:34	Full code for reproducing the bug: channel C extends ned.DatarateChannel { int foo @unit(Gbps); datarate = foo; } module Node { gates: inout g; connections allowunconnected: } network Net { submodules: a: Node; b: Node; connections: a.g <--> C <--> b.g; } omnetpp.ini: [General] network = Net **.foo = 42

(0000952) andras (administrator) 2014-11-28 13:33	Problem is twofold: (1) parameters are initialized in the order of declaration, basetype-to-subtype, and top-down (within a type) order. Then, datarate=x should cause a "parameter x not yet initialized" error. This doesn't happen due to another issue: (2) during in the parameter initialization stage, it is not checked that a referenced variable has indeed been already initialized. Therefore the construction-time value of x (zero) is used for datarate. (Note that this can no longer happen when module initialize() is called, as all parameters are guaranteed to be initialized by that time.) Issue (2) can be easily fixed. (1) is more difficult, as the parameter initialization strategy itself has to be modified to be more flexible.

(0000954) andras (administrator) 2014-11-30 07:29	Fixed. Parameters of the same module/channel can freely cross-reference each other, as long as they are no cycles. Cycles are reported as errors.

Relationships