>From: "Bresticker, Shalom" <shalom.bresticker@intel.com> >By the way, it was already done in this production: > >array_method_name ::= > method_identifier | unique | and | or | xor > >It IS ugly. > >But there is a precedent. That is unfortunate. I may even have run across this before, but blocked it out of my memory. Though there is precedent, it is still undesirable. So it is still a reason why "next" is a particularly bad choice for a new keyword. The situation that Gord pointed out, where "next" is used as an identifier in the standard package, is an even stronger reason. This is in addition to the fact that it collides with so many identifiers in designs. Steven Sharp sharp@cadence.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Mar 27 17:43:32 2008
This archive was generated by hypermail 2.1.8 : Thu Mar 27 2008 - 17:46:37 PDT