|
Do you still feel the same way?
Not really. I still find it an easier approach for simple situations - but greater familiarity with Java etc. has made me appreciate the notion of throwing errors more. However ... Are you listening Barbara? <grin> - I do think we need support for a an RPG implementation of throw(). The problem right now is that when you throw an exception you still need some kind of return code in the background because RPG only signals a generic code to Monitor. There are hundreds of available status codes - it would be nice if a block was allocated as User Defined and the throw op-code allowed you to specify a specific status code that you were signaling. If I had that I'd use it for most everything. Monitor is wonderful - but it needs throw() to make it complete. Jon Paris Partner400 www.Partner400.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.
midrange.com
