From: Stephen W. <st...@ic...> - 2020-05-16 21:53:01
|
It makes sense to be strict about the syntax. There are likely lots of people who learn Verilog syntax from Icarus Verilog behaviors. The "@ *" vs. "@*" might be construed as an actual bug. If that's the case, then I would suggest NOT accepting the extended version, even in a generous mode. However, you are really going to have to convince me that @* is a single token. Pretty sure that is not the case. The standard has in the beginning an exhaustive list of all the lexical tokens, and @* is not listed there. Also, consider that @* and @(*) are specifically called out as valid. On Mon, May 11, 2020 at 12:38 AM Cary R. via Iverilog-devel <ive...@li...> wrote: > > I have found a couple things that could be considered enhancements, but are clearly not supported by the standard. My question is should we have these enhancements controlled by a flag of some sort so people can restrict Icarus to only accept what is supported by the standard? For example pullup/pulldown should only support a single port. @* is really a single token and the binary ~& and ~| are not in the standard. There may be more. Is some new strict flag the correct thing for this? I think @* not being a single token is a bug and probably should be fixed. I'm personally of the opinion only standard/commonly supported functionality should be enabled by default and an extension flag should be used to enable the rest of this if it is kept. > > This would likely require reworking some of the tests to pull out the enhancements to have them be in a separate file. > > Thoughts? > > Cary > _______________________________________________ > Iverilog-devel mailing list > Ive...@li... > https://lists.sourceforge.net/lists/listinfo/iverilog-devel -- Steve Williams "The woods are lovely, dark and deep. st...@ic... But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." |