Bernie-
Yes, it doesn't matter.
We use WHILE 1 = 1 THEN a lot as well.
I was just saying that it is usually better to have the constants on the
right and <variables> on the left when using logical operators. Besides,
that's how we give variables their values.
Rommel
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
Behalf Of Bernie Corrigan
Sent: Friday, April 27, 2001 2:46 PM
To: [EMAIL PROTECTED]
Subject: RE: Infamous I> prompt (Code)
Rommel -
It doesn't matter. A lot of us use things like WHILE 2 > 1 THEN or
IF 2 > 1 THEN to trigger things we always want to happen.
Bernie
_______________________________________
At 11:46 AM 4/27/2001 -0700, you wrote:
>Ken,
>
>In the following code:
>
> *(If current issue is larger than average)
> *(Move from current to future)
> IF 0 > .vRDDIFF THEN
>
>
>It is usually good practice to keep constants on the right side of the
>operator and variables on the left.
>
> IF vRDDIFF > 0 THEN
>
>
>
>Rommel
>
> -----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
>Behalf Of Ken Godee
>Sent: Friday, April 27, 2001 10:25 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Infamous I> prompt (Code)
>
> << File: Text from file 'loadavg.cmd'.txt >> I've dotted all my Vars,
added
>indicator vars to fetch statements
>all vars intialized outside of whiles, set whileopt off, increased files
>from 5 to 30 still blows out to "I>" prompt (runs under
>trace/debugger). If anyone wants to take a minute and peak at the
>code and see if there is anything I'm missing, I've attached the
>code ( not sure if list server excepts attachments) the show vars
>are just for testing program.
>
>
>
>
>
>
