OMNeT++/OMNEST Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000391OMNeT++simulation kernelpublic2011-08-05 13:142011-08-30 15:41
Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
PlatformOSOS Version
Product Version4.2b2 
Target VersionFixed in Version 
Summary0000391: Allow connections defined in a baseclass to be overridden in a subclasses.
DescriptionSee EthernetInterface in INET for an example.

It contains some special IHook module vectors to allow injecting behavior into the NIC. This makes harder to understand the module's internal structure and it is not used 99% of the time. It may also be insufficient and we could potentially insert them everywhere.

The goal is clear: we have to have a way to customize connections without copying the whole module and editing the connections section. If we were subclassing EthernetInterface and override the connections in the subclass, then we would clearly be in a much better situation. The subclass would only contain the differences and the base class would not know about that at all.

Suggested syntax:

module MyEthernetInterface extends EthernetInterface {
      myCustomSubmodule: MyCustomSubmodule;
      netwIn --> { @override(); } -->;
      myCustomSubmodule.out --> { @override(); } -->;
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
andras (administrator)
2011-08-30 15:41

Use @reconnect instead of @override, it's more explicit...

- Issue History
Date Modified Username Field Change
2011-08-05 13:14 levy New Issue
2011-08-30 15:41 andras Note Added: 0000538

Copyright © 2000 - 2022 MantisBT Team
Powered by Mantis Bugtracker