|
> You would have the same problem whether you were using Java or not, for this > specific instance anyway. It is an RPG ILE flaw that you can't easily throw > your own errors and have the MONITOR block catch it. Not saying you're > wrong, Scott, just qualifying your statement some more. True, but you could design your error reporting so that you don't have to use MONITOR. As we've already discussed on this list, MONITOR needs to be further enhanced for it to be really useful. The ability to easy/quickly load the error info into some sort of exception data structure would be nice. It'd also be nice if we could easily throw our own errors. Naturally, we can do those things with APIs, but I think this is stuff that should be easy to do for the average programmer, since it's something that everyone needs to be able to do. Right now, MONITOR gives us very little that we couldn't already do with %error and %status.
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.