Re: Adding array elements...

Hi Ken,

I see your point and it is a valid one. In my case it is not a concern as
the array is reset to blanks prior to calling the procedure so a blank value
can only represent an array element that has not yet been populated.
In a prior thread this solution was resolved (by Scott's suggestion) by
incrementing a global variable within the procedure which was initialized
prior to the first call to the procedure.
I think it was one of those days where the coffee had not yet taken effect
and I just missed the simple solution.

Robert Rogerson

On Thu, Oct 14, 2010 at 11:50 PM, Ken Sims <mdrg8066@xxxxxxxxxxx> wrote:

Hi Scott -

On Thu, 14 Oct 2010 12:04:54 -0500, Scott Klement
<rpg400-l@xxxxxxxxxxxxxxxx> wrote:

So I find myself wondering why you'd ever use %lookup? Why search the
array when you can simply add 1 to a number? Not only is adding more
obvious to the person reading the code, it's also much more efficient
for the computer.

Another consideration, which I don't think would be a concern for this
specific situation, but definitely applies when thinking about the
concept in general ...

If your lookup value is a valid array element value, you can overwrite
an element. The +1 method eliminates this possibility.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.