Randy, I will get back to the rest of your email later, but I wanted to respond to one item now. >In the spirit of compromise, I'd be willing to >consider separating the two lists if we could retain the keyword, >config, in the Verilog source keywords. This would at least allow us to >implement a messy lexical analyzer mode change based on this keyword. I appreciate the spirit. If this would have resolved the problem, I might have suggested something similar myself (even though I strongly dislike context sensitive lexing). Unfortunately, the keyword "config" is the main cause of keyword conflicts. In our suite of 67 real customer designs that we use for testing, "config" is used as an identifier in 7 designs (or 10.5%). An additional 3 designs (4.5%) used "cell" as an identifier. None of the other config keywords appeared . So eliminating all of the config keywords except "config" wouldn't help much. Changing to less-used keywords to replace "config" and "cell" would solve the main problem, but would not be backward compatible. Steven Sharp sharp@cadence.comReceived on Thu Apr 21 16:45:10 2005
This archive was generated by hypermail 2.1.8 : Thu Apr 21 2005 - 16:45:47 PDT