<snip> I think these two separated points from the same post are to some extent in conflict. If the only documentation of an interface is the macro that invokes it ... </snip> I do not see a conflict..
I did not say that the macro is the documentation. I said that the book is the documentation. The fact that mappings might be available for parameter lists often does not mean that that mapping is intended for you to use to build your own. For example, it might be intended for the macro to use and rely upon, or it might be provided for diagnostic reasons. And the change for which I gave an example that would break misuse of an interface did not involve recompilation. But it was incompatible if you did not follow the documented rules. We do not, in general, ever expect to get the user community to recompile. And as a result you can be quite confident (in the absence of documentation to the contrary such as migration information about an incompatibility) that if you mimic the expansion exactly (by whatever mechanism you do so), you will have something that works and continues to work. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
