Raise an error when preprocessor finds an not known define

Yes.  Either -pdr or -pdsw195 will emit a warning specifically for this case.

cl6x -pdsw195 test.c
"test.c", line 1: warning: zero used for undefined preprocessing identifier.

You could also use a #error directive as in:

#ifndef configPARAMETER

#error Missing definition:  configPARAMETER must be defined

#endif

Mateja

Hi Archaeologist,

thanks for your answer. To be honest, where do I find the information that 195 is about undefined macros where 0 is assumed.

Is there a table to look those things up?

Thanks again.

JD

Mateja Putic,

thanks for the hint,

Archaeologist gave the right answer,

what you are writing is true but in a project with thousands of macros you would not write it in your proposed way.

Nevertheless, thanks for your contribution.

JD

Julian Dieterle said:

where do I find the information that 195 is about undefined macros where 0 is assumed.

Use -pden (AKA --display_error_number) in combination with -pdr to see the ID number for the diagnostic.

% cl6x -pdr -pden -pdv file.c
"file.c", line 1: remark #195-D: zero used for undefined preprocessing
          identifier
  #if VAR_NOT_DEFINED
      ^

Note the use of -pdv (AKA --verbose_diagnostics) is what causes the problem line to be echoed.

For those who inherit a project or make file with mystery options like -pdsw195 in it, you can look up the meaning of diagnostic ID #195 here http://tiexpressdsp.com/index.php/Compiler_Errors_Warnings .

Thanks and regards,

-George

That's it!

Thanks!

JD