This behavior is by design. The command should create a signal called "oneshot.1.time-left" and connect it to "wcomp.5.in". In HAL, signal names and pin names are permitted to be the same, and it is not an error to list a single pin in a "net" command. -- jepler
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
However.... I strongly discourage using signal names for net names, and
that most likely not what someone who types "net pinname pinname" has
in mind.
I'm tempted to change 'net' so it complains if you ask for a signal
name that is already a pin. That would force people to name their
signals something meaningfull, and catch a common user error (missing
net name).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
This behavior is by design. The command should create a signal called "oneshot.1.time-left" and connect it to "wcomp.5.in". In HAL, signal names and pin names are permitted to be the same, and it is not an error to list a single pin in a "net" command. -- jepler
Logged In: YES
user_id=774940
Originator: NO
However.... I strongly discourage using signal names for net names, and
that most likely not what someone who types "net pinname pinname" has
in mind.
I'm tempted to change 'net' so it complains if you ask for a signal
name that is already a pin. That would force people to name their
signals something meaningfull, and catch a common user error (missing
net name).
Logged In: YES
user_id=2772
Originator: NO
I've implemented this warning on the 2.1 branch and on TRUNK. I'm tempted to go ahead and make it an error on TRUNK. Thoughts?
Logged In: YES
user_id=2772
Originator: NO
It's now an error on TRUNK and a warning in 2.1.6.