No feature tests in the header file. As long as the header hasn't already been used it unconditionally defines the data areas and the function prototypes.
I'd accept feature test macro(s) as a reasonable alternative as long as MetalC programs can use just the data area definitions and not the function prototypes. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, August 13, 2018 6:10 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Using the Binder API and MetalC On Mon, 13 Aug 2018 18:29:30 +0000, Farley, Peter x23353 wrote: > >... for future maintainability it sure would be nice if IBM split the >/usr/include/__iew_api.h into two parts - Data definitions and function >prototypes. > >Or create two new header files for each and make /usr/include/__iew_api.h just >#include the two new headers to preserve the current functionality. > Or. conditional compilation. Might there already be a feature test macro for MetalC? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
