RE: FOR loop limit

To me it's a bit overkill to ask the compiler to give an error (a level
10 warning maybe) if your counter field is potentially too small.

Also, if you're asking for it on the For, you should also ask for it on
a Do*.

d x S 3p 0

DoU x > 999; // or DoW x <= 999;
X+= 1;
EndDo;

You'll get the same run-time error here.

And I'd like to second everyone who said to use signed/unsigned integers
instead of packed/zoned fields for the purpose of a counter.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Crispin Bates
Sent: Thursday, January 29, 2009 3:57 PM
To: RPG programming on the IBM i / System i
Subject: Re: FOR loop limit

Mark,

Do you mean literals assigned to vairables that are uesd for the "from"
"to"
"by" values, or actual literals in the construct?

i.e.

For x = 1 to 999 by 10;
...
endfor;

or (BTW, I was surprised the following compiled with my reckless field
naming, but I digress :-)

from=1;
to=999;
by=10;

For x=from to to by by;
...
Endfor;

If the former, then yes, I can see that in that instance the compiler
might
possibly be able to know, although I'm not sure I really think it should

have to...

Crispin.

----- Original Message -----
From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, January 29, 2009 4:23 PM
Subject: Re: FOR loop limit

Hi, Crispin:

No, I was not thinking of anything like that.

But the compiler should be able to detect if a FOR loop coded with
literal numbers specified for the "from" and "to" limits and "by"

value

will exceed the size of the index variable, especially if it is a
"packed decimal" type. In other words, based on the size required to
store the "to" value, plus the "by" value, apparently, the way RPG IV
works... :-o

Cheers,

Mark

Crispin Bates wrote:
Mark,

Are you suggesting that the compiler should be able to follow program

logic
to determine what the value of the limit is prior to the for loop?

That

value could have been set anywhere in the program before the loop was

hit.
Yes, in the simple example it was the statement before, but...

Maybe I missed your point :-)

--
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.