Based on your little example, one possibility is that original programmer
assumed that num will be automatically initialized to a non-zero value.
Automatic (local) storage is undefined, meaning you get whatever is in the
stack at that time (as my data structures professor used to say, you get
garbage).
So perhaps you've just been getting lucky all this time because the value in
the stack was always greater than zero and now on V5R3 OS has changed
slightly and value happens to be zero.

If you really want it to always be zero, either make it static storage or
explicitly initialize it to zero (i.e. int num = 0).

Elvis

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: Re: [C400-L] upgrade from V5R2 to V5R3.

Uumm. For some reasons the while (num=num) in our V5R2 was being
executed as true even when num=0.

Strange.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.