|
midrange.com
A common technique, before ILE and prototyped parameters, was to move
parameters around. This was often done, not for memory management issues,
but to control tighter which parameters were changeable by the called
program. Normally this was done in the calling program, therefore removing
any sense of trust in the called program.
I don't know if this would be a performance issue or not. But some of this
performance logic is in violation of the 80/20 rule. Which basically means
try to tune the real performance hogs first and go after the piddly crud
later if at all. Much like some people code everything inline and avoid
subroutines. Theory being that what was paged in would be what was getting
worked on. Mostly not applicable on anything larger than a B10 with only
4mb of memory.
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
"Joe Giusto
\(E-mail\)" To: <RPG400-L@midrange.com>
<juicenetdps@cross cc:
winds.net> Subject: RE: *ENTRY PLIST
(was: RE: Pointer not set for location
Sent by: .....)
owner-rpg400-l@mid
range.com
05/31/01 04:42 PM
Please respond to
RPG400-L
Are there any performance issues with using entry parm fields throughout
the
program to do work? Like memory paging because the address of the parm is
so far away from the address of the rest of the program running?
Sounds like a dumb question, but I ask because I just don't know. (think I
read or heard it somewhere long ago and started moving all my entry parms
to
work variables and then passing back anything needed in the term
subroutine.
Joe Giusto II
Programmer/Analyst
Ritz Camera
Beltsville, MD
301-419-3209 x347
410-813-2812 x347
original message:
Rob sez:
>> %PARMS again?
<snip>
As far as I am concerned the only good use for %parms is if it is equal to
the total number of parms available then you don't have to check each one
individually. Or, does it assume that if you send the last parm then you
sent all?-->>
+---
| 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
+---
+---
| 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-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.
