Don, There are good reasons to use special macros rather than something based on a system task. Macros are replaced during preprocessing/parsing, when the tool definitely knows about files and lines. There is currently nothing in the language that requires keeping that kind of information past that point. Tools may do so to assist in their debug features, but nothing in the language itself requires it. In contrast, parsing cannot do anything with system tasks. In the implementations I am aware of, the overriding of system tasks by user-defined ones is done at a later stage. You cannot assume that a system task enable is calling a built-in task until that point. The special macros are a better fit to the situation. There are good reasons why other languages use that approach. And for users who are used to those other languages, that also makes this seem more natural. 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 Wed Oct 10 13:31:18 2007
This archive was generated by hypermail 2.1.8 : Wed Oct 10 2007 - 13:31:57 PDT