<snip> 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. </snip>
OK, I'll bite. Why is it important to separate the data from the function prototype? Isn't the existing one syntactically correct? It might not be usable in Metal C, but does its presence cause you harm? Could you use #define to "change" the name to something else if you needed a different name? And, out of curiosity, do you have a requirement to avoid an LE runtime for whatever you are doing here? Metal C is intended to solve a problem, it is not intended to let you do everything you can do in C. Perhaps what you really want is, in addition to what is there, a function prototype that would let you provide the target address (e.g., iewxxxx_byaddr). You would have to get that address (such as by LOAD through __asm). That pre-supposes that the target routine actually supports a call using a "standard" parameter list which it sounds like the binder API's do. If an additional function prototype would help, that would be a reasonable thing to ask for. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
