OMNeT++/OMNEST Bug Tracker - OMNeT++
View Issue Details
0000714OMNeT++simulation kernelpublic2014-01-31 14:312014-02-10 21:20
till 
andras 
normalminoralways
resolvedfixed 
4.4 
4.4.1 
0000714: signal property type attribute requires namespace
When the type attribute is used in a signal property the namespace must be defined for classes despite the namespace affiliation of the module.
Example:
- I have a namespace set in the package.ned (myNamspace)
- I have the same namespace (myNamspace) set in a msg-file (MyBarMessage.msg)
- When I refer in a module definition to the message defined in the msg-file, I have to specify the namespace:
@signal[foo](type=myNamspace::MyBarMessage);

In my eyes the ned file should regard the namespace defined in package.ned to find the correct message definition:
@signal[foo](type=MyBarMessage);

I don't know if it is intended behaviour, if it is please close this bug!

No tags attached.
Issue History
2014-01-31 14:31tillNew Issue
2014-01-31 14:55andrasNote Added: 0000893
2014-02-10 21:20andrasStatusnew => resolved
2014-02-10 21:20andrasFixed in Version => 4.4.1
2014-02-10 21:20andrasResolutionopen => fixed
2014-02-10 21:20andrasAssigned To => andras

Notes
(0000893)
andras   
2014-01-31 14:55   
You are right, it would make sense to observe @namespace. I'll check the code.