FOR op-code

Second the idea about %TRIM.  But since we're on the subject of
wish-lists...

I wish the FOR op-code did away with the TO/DOWNTO and instead looked at the
sign of the BY increment.  There would also have to be a change in the way
the limit value and the index are compared.

I'd like to be able to do things such as:

EVAL      START =  1
EVAL      LIMIT = 10
EVAL      STEP  =  1
FOR       INDEX = START TO LIMIT BY STEP

EVAL      ARRAY(INDEX) = something

ENDFOR


and:


EVAL      START = 10
EVAL      LIMIT =  1
EVAL      STEP  = -1
FOR       INDEX = START TO LIMIT BY STEP

EVAL      ARRAY(INDEX) = something

ENDFOR


So that I can fill an array 'forwards' or 'backwards', for instance.   This
seems more 'natural' to me.



Tom



 |  -----Original Message-----
 |  From: boldt@ca.ibm.com [mailto:boldt@ca.ibm.com]
 |  Sent: Tuesday, December 11, 2001 16:18
 |  To: rpg400-l@midrange.com
 |  Subject: Re: How do you move a text 30 char long to a field?
 |
 |
 |
 |  Bob wrote:
 |  >...
 |  >But what would be on my wish list, is to enhance the
 |  %TRIMx() built-in
 |  >functions to support a second parameter. The second
 |  parameter would be a
 |  >list of characters that are to be "trimmed" off the field's value.