Nice article Barbara, thank you! I'll be sharing this with co-coworkers.

I've recently re-boarded the "RPG exception bus" and introduced the
throw()/catch() in some of my new code at my current place of employment.

The only problem I've hit, when adding such procedures to existing is the
need to rethrow() to cross a *PGM boundary.

Charles


On Fri, Mar 5, 2021 at 11:12 AM Barbara Morris <bmorris@xxxxxxxxxx> wrote:

On 2021-03-04 7:34 a.m., Buck Calabro wrote:
On Wed, 3 Mar 2021 at 17:11, Dave <dfx1@xxxxxxxxxxxxxx> wrote:

... In my opinion, when people in your group have a calm discussion
about the relative merits of C/SQL-style return codes vs Java/IBM
i-style exceptions, you're moving in the right direction for creating
a system that is robust. No, it's really not possible to 'handle'
every single error that can occur, but when I *think* about doing that
as a standard way of building an application, the results turn out
better for me. ...

I wrote a blog post in the RPG Cafe about the issue of return code vs
exceptions for a procedure, and how to write a procedure that allows the
caller to choose: https://ibm.biz/rpgcafe_return_code_vs_exception

(Actual URL is https://www.ibm.com/support/pages/node/1119309)

--
Barbara

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.