In all sub routines and stored procedures, I normally declare all the
variables at the beginning of the routine, and clear the ones I don't
want to stay around afterwards at the end.
Albert
On 28/07/2014 8:04 AM, Karen Tellef wrote:
Don't use WHILEOPT ON. Just my personal opinion, your mileage may
vary, but with the speed and capacity of modern computers, I don't
think you get the gains that we used to see back in DOS days with slow
computers when we appreciated having this option. So to me it's not
worth making the "mistakes" that kind of break Whileopt and chew up
memory in the background.
Karen
-----Original Message-----
From: Michael J. Sinclair <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Mon, Jul 28, 2014 8:13 am
Subject: [RBASE-L] - Creating Variables in large applications with
while loops/whileopt on
Hi All,
I was reading about whileopt. To make it work well, one of the
requirements is to create all of the variables outside of the while
loop. I assume (correct me if I am wrong please) that this also
applies to any RUN statements within the while loop.
How do professional programmers create variables? Do they create all
variables needed at the beginning of the application including all the
sub routines? Should subroutines not be allowed to create variables
just in case they are ever used within a while loop? Does having
hundreds of variables created at the beginning of a large application
make sense?
TIA
Mike
