Difference between revisions of "Category:Service Procedures"
DaveLClarkI (talk | contribs) (Undo revision 12861 by DaveLClarkI (talk)) |
DaveLClarkI (talk | contribs) (→Summary) |
||
| Line 1: | Line 1: | ||
[[Category:Categories]] | [[Category:Categories]] | ||
==Summary== | ==Summary== | ||
| − | This category contains sample service procedures. | + | {{AN}} are the smallest (and only) executable portion of a [[service program]]. This category contains sample service procedures. |
{{stub}} | {{stub}} | ||
| + | |||
== Justification == | == Justification == | ||
There excellent reasons for having service procedures—such as shareability and standardization of business rules. However, some service procedures (minus their error checking) are so small that one might question creating a service procedure at all. They might feel that simply employing the stripped-down code directly within their program code is the best way to go (saving the necessity of calling a separate routine—with the additional overhead that such action would require). | There excellent reasons for having service procedures—such as shareability and standardization of business rules. However, some service procedures (minus their error checking) are so small that one might question creating a service procedure at all. They might feel that simply employing the stripped-down code directly within their program code is the best way to go (saving the necessity of calling a separate routine—with the additional overhead that such action would require). | ||
Revision as of 15:56, 12 December 2018
Summary
Service Procedures are the smallest (and only) executable portion of a service program. This category contains sample service procedures.
This article is a stub. You can help by editing it.
Justification
There excellent reasons for having service procedures—such as shareability and standardization of business rules. However, some service procedures (minus their error checking) are so small that one might question creating a service procedure at all. They might feel that simply employing the stripped-down code directly within their program code is the best way to go (saving the necessity of calling a separate routine—with the additional overhead that such action would require).
| Sometimes, having a service procedure is simply a means of making code more self-documenting (i.e., easier for others to understand). |
To wit... Which would you rather see in an RPG program—this?
if %subst(myLongString:%len(myLongString)-4+1:4) = 'TEMP'; // do something endif;
...or, this?
if GenUtl_RightString(myLongString:4) = 'TEMP'; // do something endif;
It is the opinion of many that the second form is more readable and is self-documenting. Hence, the reason for some of these very small service procedures.
Pages in category "Service Procedures"
The following 34 pages are in this category, out of 34 total.
