Separate name from width #20

Merged
TheZoq2 merged 1 commit from name_width_separation into main 2023-10-23 13:28:03 +00:00
TheZoq2 commented 2023-10-05 15:58:27 +00:00 (Migrated from github.com)

It is useful to have both around, but for things that look for particular signals by name, having the width always included in the name is problematic. For example in https://gitlab.com/surfer-project/surfer/-/issues/59

CC: @oscargus since you made the original change

It is useful to have both around, but for things that look for particular signals by name, having the width always included in the name is problematic. For example in https://gitlab.com/surfer-project/surfer/-/issues/59 CC: @oscargus since you made the original change
oscargus commented 2023-10-05 17:35:57 +00:00 (Migrated from github.com)

I agree that both may be useful to have it. Even more useful to combine signals with the same name and different indices (which seems to be how e.g. ModelSim generates VCDs by default).

I agree that both may be useful to have it. Even more useful to combine signals with the same name and different indices (which seems to be how e.g. ModelSim generates VCDs by default).
oscargus (Migrated from github.com) reviewed 2023-10-05 17:38:32 +00:00
oscargus (Migrated from github.com) commented 2023-10-05 17:38:14 +00:00

For the ModelSim use case this parameter name is maybe not the most obvious. The only thing we know is that it contains an index or a range.

Not a big deal though.

For the ModelSim use case this parameter name is maybe not the most obvious. The only thing we know is that it contains an index or a range. Not a big deal though.
Sign in to join this conversation.
No description provided.