Adam,
Do you have a link to the article? I probably saw it bit it doesn't sound familiar at the moment.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam Glauser
Sent: Friday, May 08, 2009 3:21 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Error messages from service program procedures, was: Call back procedures
Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
At this point the design looks like this:
1) Service program containing edit procedures common across multiple transactions. One procedure per edit. Each procedure returns a pass fail indicator and an error message as the first parameter.
You may want to reconsider the 'first parameter is error message'
design. That's how I started out doing things. The extra overhead of passing in error-related parameters every time doesn't seem like much, but it gets really tiresome and IMO reduces readability of the code.
If I were starting from scratch, I would prefer the 'global error info'
procedure suggested by Scott's article "Writing Reusable Service Programs"*, in particular the sections titled "Statelessness" and "Error Handling".
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
midrange.com
