I don't have a problem with either of the proposed switches being suggested. I do not like the idea of removing Verilog configs from source files. There will already be a backwards compatibility issue since there are customers currently relying on such functionality. I would be opposed to removing the keywords from the keywords list even though I acknowledge the issues with Verilog-1995 designs. Making this change will introduce a double incompatibility issue for vendors that did provide support for 1364-2001 configurations in Verilog source in that such vendors will end up supporting both 1364-2001 with the keyword restrictions and 1364-2005 without. Between this and the customer design changes necessary for such a change, we do not believe that removing source support is a good solution. Gord. Steven Sharp wrote: > As part of my proposal for 1364 erratum 350, I was asked to put in an > informative note that suggests a command line option for tools to use > to specify that an input is a config file. The goal is to encourage > tools to use the same option. To help with this, I need to pick an > option that is not already used by many tools for something else. I was > asked to query the members of these lists to find out if anyone was > aware of tools using these options. > > The options that have been proposed are "-cfg" and "-config". Is anyone > aware of tools using either of these? > > Steven Sharp > sharp@cadence.com > -- -------------------------------------------------------------------- Gordon Vreugdenhil, Staff Engineer 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.comReceived on Mon Apr 18 08:57:42 2005
This archive was generated by hypermail 2.1.8 : Mon Apr 18 2005 - 08:58:20 PDT