Date: Tue, 29 Jul 2008 12:33:39 -0400
Reply-To: "Howard Schreier <hs AT dc-sug DOT org>"
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Howard Schreier <hs AT dc-sug DOT org>"
Subject: Re: tip: Macro Design Checklist
On Tue, 29 Jul 2008 12:01:24 -0400, Fehd, Ronald J. (CDC/CCHIS/NCPHI)
>> From: data _null_,
>> I would suggest using SAS data sets or other more conventional SAS
>> tools. I find using INFORMAT or FORMATS where in the past I would
>> have used macro variables to be much more powerful and easier to code.
>> I have been experimenting with finding conventional SAS techniques to
>> to replace much of the work I would have done with macros or macro
>> language. It has given me a whole new outlook and changed my coding
>> and enhanced the enjoyment of trying to write SAS programs.
>"Look! Krewe! No Macros!"
>This suite was initially just a personal challenge to myownself
>to replace my FreqAll macro.
>While the InTheKnow crowd has been talking about
>parameterized include programs
Crowd? Hmm. The Google search string
sas "parameterized include" -fehd
returns two hits, both of which point to articles Ron has written on the sC wiki
>SmryEachVar is a demo of the power of Data _Null_
>to call execute parameterized includes.
>Check out the work-horse routine of the suite: CallXinc.sas
>Modules calling CallXinc:
>Note: I did not say
>"Look! Krewe! No Macro Variables!"
>for in-line conditional processing see:
>Ron Fehd The Maven, formerly known as
> the macro maven CDC Atlanta GA USA RJF2 at cdc dot gov