Robert A. Rosenberg wrote:
Will using this use of ifndef solve the issue that if a compiler option is set at launch time due to being coded in
the JCL or via a DD it can/will override the pragma supplied setting?
There are so many "things" in C/C++ compilation I have to look back in this thread and see what specifically you're up
against.
If you posted the exact problem.
Let me go to the archives and get back to you.
The issue that was raised is that there is apparently no way to override the global settings via a pragma in the
source code of a module being compiled. Unless this happens all the ifndef does is supply options to be used when
compiling under Z/OS SO LONG AS THE COMPILER does not override the requested option due to a Global Default override.
There's "compiler options" like what kind of error output goes where, and there's "compiler options" like how the C/++
preprocessor interprets stuff and they overlap.
Off to check on what you reported as your specific problem.
If you didn't previously post in detail, please repost with detailed description of JCL-set compiler option, any
pragmas, what you want, etc.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
