× 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.


  • Subject: RE: *ENTRY PLIST (was: RE: Pointer not set for location .....)
  • From: "Joe Giusto \(E-mail\)" <juicenetdps@xxxxxxxxxxxxxx>
  • Date: Thu, 31 May 2001 17:42:40 -0400
  • Importance: Normal

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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.