31b4ac5cec
This patch turns the existing warning into a fatal, as there should never be any cases where a (non-vector) port is assigned to and then later connected to something else. If this behaviour is allowed, as it used to be, there are cases where the wrong number of C++ ports are created when instantiating objects with VectorPorts (obviously that could be fixed, but the better approach is to simply not allow it). |
||
---|---|---|
.. | ||
internal | ||
objects | ||
stats | ||
util | ||
__init__.py | ||
config.py | ||
core.py | ||
debug.py | ||
event.py | ||
main.py | ||
options.py | ||
params.py | ||
proxy.py | ||
SimObject.py | ||
simulate.py | ||
ticks.py | ||
trace.py |