>From: "Bresticker, Shalom" <shalom.bresticker@intel.com> >> If a user >> defined such a system function named $inferred_clock, then >> the syntax $inferred_clock used in an expression would refer >> to that system function, not to the special meaning in this >> proposal. That seems like a problem. > >I don't think so. The number of user-defined system tasks and functions >is orders of magnitude less than the number of user-defined identifers. I agree that it is unlikely to happen by accident, especially with the names chosen. The bigger issue is whether we want to allow users to do it on purpose. There is a difference from identifiers. A keyword takes precedence over a user-defined identifier. A user cannot use an identifier such as "for" and replace the keyword. But a user-defined system task or function takes precedence over built-in ones. So a user could define a system function named $inferred_clock and replace the built-in meaning. It seems to me that this might be undesirable. 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 Tue Mar 18 14:44:14 2008
This archive was generated by hypermail 2.1.8 : Tue Mar 18 2008 - 14:44:39 PDT