Re: Trace XL C Preprocessor input

On Fri, 23 Jun 2023 19:00:02 -0500, Eric Erickson wrote: >Using XL C on z/OS V2R5. I've got a set of #ifdefs in a header file that are >not giving me the results I expect. I know on other compilers I've used in the >past that there were options to output all input statements showing the

Re: Trace XL C Preprocessor input

See here SKIPS(SHOW|HIDE) The SKIPS(HIDE) also known as SKIPSRC shows you what is used, and suppresses text which is not used. I found this useful trying to find the combination of #define … to get the

Re: Trace XL C Preprocessor input

Sprinkle a bunch of #warning "I'm here" in all code paths. Unique messages of course. - KB --- Original Message --- On Saturday, June 24th, 2023 at 5:30 AM, Eric Erickson wrote: > Using XL C on z/OS V2R5. I've got a set of #ifdefs in a header file that are > not giving me the

Re: Trace XL C Preprocessor input

SHOWINC? (+ SOURCE) On Fri, 23 Jun 2023 19:00:02 -0500, Eric Erickson wrote: >Using XL C on z/OS V2R5. I've got a set of #ifdefs in a header file that are >not giving me the results I expect. I know on other compilers I've used in the >past that there were options to output all input

Trace XL C Preprocessor input

Using XL C on z/OS V2R5. I've got a set of #ifdefs in a header file that are not giving me the results I expect. I know on other compilers I've used in the past that there were options to output all input statements showing the #ifdefs and how the logic was processed. I need the same thing for