0000714: signal property type attribute requires namespace

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000714

OMNeT++

simulation kernel

public

2014-01-31 14:31

2014-02-10 21:20

Reporter

till

Assigned To

andras

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

4.4

Target Version

Fixed in Version

4.4.1

Summary

0000714: signal property type attribute requires namespace

Description

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!

Tags

No tags attached.

Attached Files

Relationships

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

Issue History
Date Modified	Username	Field	Change
2014-01-31 14:31	till	New Issue
2014-01-31 14:55	andras	Note Added: 0000893
2014-02-10 21:20	andras	Status	new => resolved
2014-02-10 21:20	andras	Fixed in Version	=> 4.4.1
2014-02-10 21:20	andras	Resolution	open => fixed
2014-02-10 21:20	andras	Assigned To	=> andras