OMNeT++/OMNEST Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000827OMNeT++simulation kernelpublic2015-05-28 09:532015-05-28 10:00
Reporterandras 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version4.6 
Target VersionFixed in Version 
Summary0000827: Configuration options should allow expressions
DescriptionInifile options should allow basic expressions to be specified as value.
Per-module options should also understand reference to module index ("index" operator), etc.

Example (from Antonio Virdis):

**.numUe = ${numUEs = 1 , 10 , 20 } # set the number of ues for 3 scenarios
num-rngs = ${val = $numUEs * 2} # each ue has 2 rng

**.ue[*].rng-0 = ancestorIndex(0) # set rngs for each UE
**.ue[*].rng-1 = ancestorIndex(0) + 1
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0001050)
andras (administrator)
2015-05-28 10:00

cConfiguration's getter methods currently delegate to the parseLong(), parseDouble(), parseBool() etc methods of the same class, which simply use atol(), parseQuantity(), comparison to "true" vs "false" and so on, without attempting to evaluate the value string as an expression.

One way to implement the feature could be to employ the cDynamicExpression (or common's Expression) class to evaluate the string and then try to cast the result to the appropriate type.

- Issue History
Date Modified Username Field Change
2015-05-28 09:53 andras New Issue
2015-05-28 10:00 andras Note Added: 0001050
2015-10-12 09:28 ammmar1988 Issue cloned: 0000847


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker