I have been experimenting with MetalC code to invoke the Binder API macros (IEWBIND) and access the returned data using the C language definitions in /usr/include/__iew_api.h.
The issue is that /usr/include/__iew_api.h also contains all of the actual Binder API function prototypes and these cannot (easily) be used from MetalC because they reside in a DLL, plus it appears to me that they are only useable in an LE enclave, also not easily done from MetalC. OTOH, the C language buffer and data area definitions are perfectly usable in MetalC as they are. I was thus forced to make a copy of the /usr/include/__iew_api.h structure and data area definitions without the function prototypes. This works well for my immediate need, but 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. Would some kind soul volunteer to set up an RFE for that? I would do so myself but for various reasons I cannot do it at this time. Peter 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
