|
> From: bmorris@ca.ibm.com > > It can bedangerous to handle conditions with an ILE condition handler, because > it causes the failing procedure to continue at the next MI instruction rather > than the next HLL instruction. I remember running into this when I was learning condition handlers. What I would REALLY like is an option to retry an operation, but again it would have to be at the HLL level. For example, a nice generic condition handler would be to notice that you're missing a library in your library list (on either a program call or a database file open). In that case, the condition handler could add the library and then tell the HLL to retry the operation. This would allow some very elegant error handling. However, it would require some serious intrusion into the compiler - you'd have to be able to "mark" HLL retry boundaries, and allow a completion method from the condition handler to restart execution at that mark. It's not impossible, but it would definitely require some serious thought. Joe
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.