I am very sympathetic to the user arguments here. I think the performance impact of such checking is relatively small. My main concern is the possibility of large amounts of existing code that does this already, particularly at initialization. Many of our customers might be very unhappy if we suddenly started spewing warnings on working designs. The possibility of standard mechanisms to turn off the warnings has been suggested, but that needs more LRM work than is appropriate at this stage of the process. We don't even know at this point how detailed that control needs to be. If it has to be on a per-instance basis, and turned on or off during particular times, then it gets a lot more complex. 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 May 7 11:53:34 2009
This archive was generated by hypermail 2.1.8 : Thu May 07 2009 - 11:53:51 PDT