×
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.
Yes, at compile time there is a CHECKOUT keyword. Don't quote me on this
but I believe option to use is *EFFECT.
We use great number of them in our compiles so I'm not sure which specific
one signals this warning. I love these warnings.
This way I write standards compatible code and have compiler weed out bad
practices.
Elvis
Celebrating 10-Years of SQL Performance Excellence
-----Original Message-----
Subject: Re: [C400-L] upgrade from V5R2 to V5R3.
At 11:33 2007-04-16 -0400, Bob Crothers wrote:
I myself would never use (num=num) in a conditional statement.
Indeed, conditions of the form lvar=expr are so often an
accident that some compilers flag them at compile time. If
you *reallY* want to write that, you wrap the embedded
assignment in another set of parentheses.
Is there a way to tell C400 to flag such constructions?
Cheers,
Terry.
midrange.com
