> Cadence implemented >most of Verilog-2001 and then got around to implementing configs. Now they >have the problem of customers using all types of Verilog-2001 capabilities, >but some of the Verilog-2001 code uses "config" as an identifier, so it is >not as easy as telling the tool that this block of code is Verilog-1995, as >I suggested in an earlier email message. Slight correction in the sequence of events here, Cliff. We discovered that the config keywords were the only ones that would cause significant problems when compiling Verilog-1995 code. We noted that configs could be kept in separate input files (which also makes sense if you recognize that they are effectively linker directives, not source code). We brought up this potential solution to the backward compatibility problem with the IEEE. While there was not full consensus, the response generally seemed positive. On this basis, we decided not to reserve the config keywords, in expectation that they would not need to be reserved. This also allowed us to compile with Verilog-2001 by default, without requiring any special command line options that you would complain about having to use. Steven Sharp sharp@cadence.comReceived on Tue Apr 26 19:00:24 2005
This archive was generated by hypermail 2.1.8 : Tue Apr 26 2005 - 19:01:15 PDT