×
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.
-----Message d'origine-----
We are obliged to code all our exported subprocedures with 2 data
structures as parameters. One for input, the other for output. The
"parameters" are actually the DS subfields. This idea was a work
around to avoid changing modules when one needed to add a parameter.
Here's an example to demonstrate why :
Procedure GetClientProductInfo
In : ClientNumber
Out : ClientProductDescriptionShort
Modification : Colleague wants to add parameter ClientProductDescriptionLong
Procedure GetClientProductInfo :
GetClientProduct ( ) //procedure that chains to client file for associated product.
CHAIN ClientProduct ProductFile // This file contains all the descriptions.
Personally, I wouldn't expect a procedure to return product descriptions for a client number. I'd have charged the client then pass the product to get the description.
Then, the argument would be that the caller would have to do several calls instead of one.
Someone help!
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
