×
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.
As others have said, I think the only wrong answer to the return value
vs. output parameters is to only use one or the other due to some
misguided policy.
That said,
Kurt Anderson wrote:
Also, forcing all output to be in the form of a return value can often times require adding a data structure to the program for no other reason than to pass multiple output fields as a return value.
I think that with some thought, the data structure return values should
all represent some sort of natural unit of information. As Scott
pointed out, customer address is a good example of this. At some point,
all of the entities you need to represent should be modelled, or you're
adding new features that require new models anyway.
Then again, I tend to think more in "object oriented" terms, and to me
the data structures tend to go hand-in-hand with *SRVPGMs.
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
