Re: Procedures

[Sam Spritzer <sspritzer@GW.CTG.COM>]

Yea, you're right....BREAK was the wrong answer.  But at least EVALUATE was the 
right one.  Anyone want to make an argument for that vs. GOTO vs. nested IFs?
I don't like nested IFs for one simple reason, its pretty confusing trying to 
decipher them.  Plus, I believe there is more overhead involved since each IF 
is called whereas with EVALUATE, you can stop it with BREAK.
Sam
P.S.  Maybe Ray can add BREAKability to IFs in the SQR wish list for ver. 7.
>>> donm@ONTKO.COM 07/12/00 19:01 PM >>>
On Wed, 12 Jul 2000 Rick_Creel@AONCONS.COM wrote:

> If he is using several IF statements, then I believe the GOTO is the
> only way to get to the end of a procedure.

Actually, if statements can be nested.  So...

begin-procedure example
   if #w
      (misc. lines of code)
   else
      if #x
         (misc. lines of code)
      else
         if #y
            (misc. lines of code)
         else
            (misc. lines of code)
         end-if
      end-if
   end-if
end-procedure   example

...is perfectly workable.

-----------------------------------------------------------------------
Donald Mellen  | Ray Ontko & Co. - Richmond, IN - http://www.ontko.com/
donm@ontko.com |  "In the beginning, there was nothing, which exploded"