%LOOKUP startindex question -- RPG400-L

× 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: %LOOKUP startindex question
From: Dan <dbcerpg@xxxxxxxxx>
Date: Wed, 14 May 2003 08:51:49 -0700 (PDT)
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

For the new %LOOKUP bif:

  %LOOKUP(arg : array {: startindex {: numelems}})

is it true that none of the arguments (arg, array, startindex, numelems) used 
in the bif are
changed by the bif?  I ask because in the old LOOKUP op code, the startindex 
value would be
changed to reflect which element was found by the operation.

TIA, Dan

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: %LOOKUP startindex question , Hans Boldt

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