Anonymous | Login | 2022-08-10 05:28 UTC | ![]() |
My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0001052 | OMNeT++ | simulation kernel | public | 2018-09-18 10:08 | 2018-09-18 10:20 | ||||||||
Reporter | andras | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||||
Status | new | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | 5.4 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001052: Module class or signal data class not found when using a module from a package with a different namespace default | ||||||||||||
Description | Module class or signal data class not found when using a module from a package with a different namespace default. Typical occurrence is when extending a project that uses namespace (like INET) with another project that uses a different namespace. OMNeT++ tries to look up the class in the second project's namespace instead of the original project (INET) where it is actually defined. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
![]() |
|
(0001373) andras (administrator) 2018-09-18 10:10 |
Cause: wrong package is searched for @namespace(): the one where the module is extended, not where it is defined. |
(0001374) andras (administrator) 2018-09-18 10:20 |
Example: project 1 with @namespace(foo) in package.ned: simple Foo { @class(Foo); } project 2 with @namespace(bar) in package.ned: simple FooExt extends Foo { } Error: bar::Foo class not found. Of course, because it's called foo::Foo. |
![]() |
|||
Date Modified | Username | Field | Change |
2018-09-18 10:08 | andras | New Issue | |
2018-09-18 10:10 | andras | Note Added: 0001373 | |
2018-09-18 10:20 | andras | Note Added: 0001374 |
Copyright © 2000 - 2022 MantisBT Team |