RE: I'd be interested in a discussion on the topic of LOOKUP vs.%LOOKUP

["Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>]

As many has mentioned, bSearch, Qsort and may be user Index are some of the 
options that will help you with V4R2 not support %lookup problem.

However, if you still choose to use LOOKUP, you might want to try this if the 
array contains a lot of "empty" element:  
1) Load the array from the back and keep track of the first non "empty" element 
position.
2) When do LOOKUP, specify the first non "empty" element position in factor 2.
        findThis        LOOKUP  Ary(fistNonEmpty).          

Above will help if speed up when not found condition happened. 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jon Paris
Sent: Thursday, January 13, 2005 8:05 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: I'd be interested in a discussion on the topic of LOOKUP
vs.%LOOKUP


The reason that %Lookup is often faster is that it implements a binary
search rather than a serial one when dealing with a sequenced array.

For V4R2 you have two options:

1) Implement your own binary search - not hard and there are many examples
on the web including RPG implementations at iSeries network among others.

2) Use the C function qsort.  Again many examples including the RPG Redbook.

Jon Paris
Partner400
www.Partner400.com