I agree that the command-line behavior is not in the scope of the standard. We do need to think about whether the compilation unit support is defined in a way that allows reasonable command-line behavior from the tools. With multiple compilation units in a single command, and macro definitions not carried over between compilation units, you could not get the desired effect if the tool just defined the macro once before starting to compile the first compilation unit. The tool would need to start with the command line macro definitions each time it started a new compilation unit. I think that would give you the behavior you wanted. Since there is a way for tools to give the desired command-line behavior, there doesn't seem to be anything we need to do in the standard for it. Steven Sharp sharp@cadence.comReceived on Thu Jul 20 15:17:27 2006
This archive was generated by hypermail 2.1.8 : Thu Jul 20 2006 - 15:17:38 PDT