From: Carsten Flensburg <flensburg@novasol.dk>

> A new way of dealing with this potential performance problem was recently
> introduced. - V5R1 added the %LOOKUP built-in-function which allows you to
> specify a fourth optional parameter specifying the maximum number of
> compares to perform.
>
> If you set this parameter to the current number of elements loaded, you
> ensure that no unneccessary compares are performed if the lookup might end
> unmatched.
>

Alternatively you could store the value looked for at the n+1'th position
(n is number of occupied positions). Then you always find it; if its
position turned out to be n+1, you know that it wasn't there.

This will work with any release.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2022 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.