|
The API header files, in general, do not provide release specific information; so the compilers will not be able to warn you about certain APIs (or API functional enhancements) not being available to you on a given release. You will need to review the V3R2 System API Reference to verify the level of APIs available to you; and obviously do some V3R2 testing of your generated code. This is an area that may change in the future, but such release tracking would most likely not be retrofitted to existing releases. Bruce > >I am developing on V4R4, compiling to V3R2, and relying on the compiler to >ensure that the code will in fact execute on a V3R2 box. Will this approach >work ? I am particularly concerned about API support ... if I reference an >API, bindable or otherwise, will the compile process let me know if the API is >not available at the target release ? >-DaveK > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.