|
JMoore wrote: >What are the performance implications of >passing large physical sized parameters? Hi J.! I haven't seen any performance ramifications; probably because the parameters aren't "passed" or moved from program to program. The caller is the only place the variable is stored. The called program refers to the parameter there, in the caller's storage. This presumes passing by reference, of course, but this is the default behaviour. Then again, this thread was about 8 characters worth of UPSI. You can't readily pass more than 256 bytes of "parameter data" with switches anyway, and decoding THAT would be a chore! nU1 nU2 nU3 nU4 nU5 nU6 nU7 nU8 = choice 0 nU1 nU2 nU3 nU4 nU5 nU6 nU7 U8 = choice 1 nU1 nU2 nU3 nU4 nU5 nU6 U7 nU8 = choice 2 etc... Buck Calabro Commsoft; Albany, NY "Nothing is so firmly believed as that which we least know" -- Michel Montaigne Visit the Midrange archives at http://www.midrange.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.