>There is a reasonable workaround for the config keyword issue. Users can do >the following [workaround using `begin_keywords "1364-2001" omitted] There is a problem with this proposed solution. The only keywords in 1364-2001 that have caused problems in customer designs are certain ones in configs. Those keywords don't really need to be reserved in Verilog source if configs are not allowed in Verilog source (which they technically are not). As a result, NC-Verilog (and possibly other tools) support a dialect of 1364-2001 that does not reserve those keywords. This dialect is very useful, since it can compile legacy Verilog-1995 without significant keyword issues, and can also compile legal Verilog-2001 designs. This means that there may be a significant amount of Verilog code by now that uses the config keywords as identifiers, but also uses Verilog-2001 features. The workaround you have suggested won't work for such code. As I mentioned in an earlier email, a compromise might be possible that takes advantage of `begin_keywords. However, that compromise needs to take into account that in practice, those keywords didn't really need to be reserved until configs were allowed in Verilog source files. So it needs to support the intermediate dialect that doesn't reserve them. Steven Sharp sharp@cadence.comReceived on Mon Apr 25 15:53:21 2005
This archive was generated by hypermail 2.1.8 : Mon Apr 25 2005 - 15:53:50 PDT