Date: Tue, 29 Jan 2002 15:25:13 -0600
Reply-To: "Gregg P. Snell" <gsnell@DATASAVANTCONSULTING.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Gregg P. Snell" <gsnell@DATASAVANTCONSULTING.COM>
Subject: Re: www.coronadoviews.com Style and Opinion
Content-Type: text/plain; charset="iso-8859-1"
I'm not sure about "institutionalize". I wasn't thinking of that aspect of
your post when I replied. To date, my roles as a SAS programmer have been
heavily skewed to the one-off ad-hoc variety, so it has rarely been an
issue. On the other hand, I would agree with an earlier post from Ian that
maintainability must be considered when developing code. And in the few
test/production environments I have worked in, I've always strived to
develop/test to the point that "no changes were necessary" to move from test
into production, including removing run statements. Especially with appdev
jsp programs, those last minute changes have almost always bit me!
From: Fehd, Ronald J. [mailto:email@example.com]
Sent: Tuesday, January 29, 2002 3:03 PM
To: 'Gregg P. Snell'; ___ SAS-L @listserv. uga. edu (E-mail)
Subject: RE: www.coronadoviews.com Style and Opinion
> From: Gregg P. Snell [mailto:gsnell@DATASAVANTCONSULTING.COM]
> For me it began when I moved off of the big iron and into PC
> land. Till
> then, I don't think I had ever coded a single 'run;' command
> because it
> wasn't necessary for batch processing. But the PC world was
> nearly 100%
> interactive and the run statements became necessary, especially if you
> wanted to submit blocks of code rather than the whole thang.
ah, so, I agree with the idea that one must have RUN;
in order to highlight and execute blocks of code within a program.
do you agree that one needs to institutionalize leaving a program ready to
be tested and debugged this way?
Ron Fehd the macro maven CDC Atlanta GA USA RJF2@cdc.gov
it must not be Friday yet