|
From: Paul Godtland <plg@us.ibm.com> > As we've been discussing, RTNEXCP has a big impact on the ability to > optimize original MI. couldn't you use a OVRPGATR-like mechanism to turn on/off optimization? The programmer could "promise" with a OVRPGATR that no exceptions will occur from now on (or that he doesn't care about things being correct if an exception *does* occur - like turning of binary size checking). This will allow optimization to proceed at the programmer's peril.
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.