OMNeT++/OMNEST Bug Tracker - OMNeT++ | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000666 | OMNeT++ | simulation kernel | public | 2013-07-25 16:31 | 2013-07-25 16:31 |
| Reporter | rhornig | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | 4.3 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0000666: Accessing volatile parameters in two-way connections causing runtime error | ||||
| Description | When using the gateA <--> {datarate = somevolatileparameter} <--> gateB connection form, it is in fact a shorthand for gateA$i <-- {datarate = somevolatileparameter} <-- gateB$o gateA$o --> {datarate = somevolatileparameter} --> gateB$i this means that 'somevolatileparameter' is accessed two times which may result in different values. The user intention is to have the same value. It would be better if the channel would be created only once and then would be cloned for the opposite direction. | ||||
| Steps To Reproduce | |||||
| Additional Information | See the following code as example: network net { parameters: volatile string areaType = default("Area_Type1"); volatile double interAreaRate = select(intuniform(0, 1), 10Mbps,100Mbps); submodules: ..... area[areas]: <areaType> like IArea { } connections: area[0].ethg++ <--> { datarate = interAreaRate; delay = 2.0ms; } <--> area[1].ethg++; ... } | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2013-07-25 16:31 | rhornig | New Issue | |||
| There are no notes attached to this issue. |