Date: Tue, 29 Jan 2002 14:41:56 -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
In-Reply-To: <9D17D648E4EBD311AD45009027D0DF9302EAE787@MCDC-ATL-64>
Content-Type: text/plain; charset="iso-8859-1"
Maven,
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.
Best Regards,
Gregg P. Snell
Data Savant Consulting
www.datasavantconsulting.com
(913) 638-4640
(208) 977-1943 fax
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU]On Behalf Of
Fehd, Ronald J.
Sent: Tuesday, January 29, 2002 2:34 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: www.coronadoviews.com Style and Opinion
> From: Ed Cabanero [mailto:ed_cabanero@YAHOO.COM]
> I've recently added some short pieces:
> Elements of style . . .
> http://www.coronadoviews.com/cover.html#elements
> b. Always end each data step and procedure with a RUN; statement
> to delineate each section of logic.
Puleeeze!
Could I ask the SAS community
what is this obsession with lotsa RUN; statements?
I recently received a program to polish: 800 lines.
Imagine my boss's surprise when I came back 15 minutes later
and said that I had reduced it to 700 lines with one find and replace:
change 'run;' to '' ;-)
I note that some procedures continue to spin
because they are waiting for a QUIT;
but there's no emphasis on ending every procedure that requires it with
QUIT;
Certainly RUN; gets the titles associated with their procedures
but do I want to advertise that I don't know that titles should come after
the step boundary keyword 'proc'?
and I do end every program and macro with RUN;
and every proc that requires it with QUIT;
Ron Fehd the macro maven CDC Atlanta GA USA RJF2@cdc.gov
By using your intelligence
you can sometimes make your problems twice as complicated.
-- Ashleigh Brilliant
By using your editor
you can sometimes make your problems twice as long.
-- RJF2
Repetition obfuscates!
Repetition reduction enhances elegance!
Repetition reduction furthers finesse!
