×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Multiple points of entry does not equate to overloaded parameters. What it means is that you can have a bunch of procedures in the same service program, and you can call each procedure directly. I have a service program that provides procedures that help me handle display files. It also contains some standard dialogs which are simple enough to be distilled into a single procedure. Generally I would expect that a program will involve many calls to procedures. Those procedures that are not specific to the program itself should be contained in one or more service programs.
Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx
-----Booth Martin <booth@xxxxxxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: 05/15/2017 05:43PM
Subject: Re: Service programs
I have a hard time seeing overloaded parameters as a benefit. They
strike me as a nerd's playground and an invitation to documentation
errors, confusion, and unexpected results in the future.
Also, it looks to me like the same underlying code gets written,
whichever solution is chosen. All that differs is how the code is
bundled and delivered.
On 5/15/2017 2:37 PM, Alan Campin wrote:
... 2. The biggest single value to a service program is that you have multiple
points of entry, you can expose multiple procedures. You break problems
down into small pieces. Their is only one point of entrance on a program.
If you want to have the program do multiple things, you have to overload
the parameters and pass control as to what you want the program to do. ...
midrange.com
