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.
Therefore, no keyword can be coded on one parameter only. The keyword
would go on the DS and thus apply to all the "parameters".

I don't have an answer to the OQ, but couldn't resist responding to this
approach. You know the risks and inflexibility that are associated with
this (flawed) attempt to be maintenance free, right? You know what happens
when you decide to make one of the DS larger, right?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Sometimes I've believed as many as six impossible things before breakfast.
-- Lewis Carroll


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2025 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.