0000391: Allow connections defined in a baseclass to be overridden in a subclasses.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000391

OMNeT++

simulation kernel

public

2011-08-05 13:14

2011-08-30 15:41

Reporter

levy

Assigned To

Priority

normal

Severity

feature

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

4.2b2

Target Version

Fixed in Version

Summary

0000391: Allow connections defined in a baseclass to be overridden in a subclasses.

Description

See 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 {
   submodules:
      myCustomSubmodule: MyCustomSubmodule;
   connections:
      netwIn --> { @override(); } --> myCustomSubmodule.in;
      myCustomSubmodule.out --> { @override(); } --> queue.in;
}

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

Notes
(0000538) andras (administrator) 2011-08-30 15:41	Use @reconnect instead of @override, it's more explicit...

Relationships