Re: [sv-bc] enum range with keyword

>Just curious, what was the original motivation behind this enum range syntax?
How is it considered useful to generate a bunch of enum names like n_1, n_2,
..., n_10 automatically?

Others like Dave obviously know more about the origin of this.

I can imagine that it might be useful for certain state machines that
have a sequence of states for counting something. And the next-state
logic might be similarly compact if all these states could be lumped
together and use the next() method to get to the next state. But you
couldn't easily assign specific values to the states, such as one-hot
values.

>And I don't really want to suggest adding any new features, but why is this
automatic name generation facility only defined for enums? Why not for wires?

This would have been better to do by adding a looping facility to the
macro processing. Then it wouldn't be limited to just names, but could
be used for a variety of things, such as generating case items. And it
would also solve the issue raised here, since the names would be generated
before being tokenized.

It does seem to be an oddball feature, that probably shouldn't have been
brought in in this form.

Steven Sharp
sharp@cadence.com

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.