Date:         Thu, 20 May 2004 13:07:42 -0400
Reply-To:     Ed Heaton <EdHeaton@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Ed Heaton <EdHeaton@WESTAT.COM>
Subject:      Re: Scope of Macro Variables
Comments: To: "Seeliger.Curt@EPAMAIL.EPA.GOV" <Seeliger.Curt@EPAMAIL.EPA.GOV>
Content-Type: text/plain

Curt,

While I think I understand what you are saying, I venture to avow that
allowing macros to declare global macro variables EMPHASIZES complexity
rather than hiding it because the users will have to study the macro
carefully to make sure they have not used a macro variable in their code
that is declared global in the macro.

Ed

Edward Heaton, SAS Senior Systems Analyst,
Westat (An Employee-Owned Research Corporation),
1600 Research Boulevard, RW-3541, Rockville, MD 20850-3195
Voice: (301) 610-4818                  Fax: (301) 610-5128
mailto:EdHeaton@Westat.com             http://www.Westat.com


-----Original Message-----
From: Curt Seeliger [mailto:Seeliger.Curt@EPAMAIL.EPA.GOV]
Sent: Wednesday, May 19, 2004 5:30 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Scope of Macro Variables


RJF2 writes:
> > 1. An invocation of a macro may fail the first time and
> >    not on the second invocation. As soon as a global
> >    macro variable is created the program environment changes.
>
> why we test in batch
> the assumption is that a macro allocates a global macro variable
> I agree, not Good Practice.

Having not gone up the learning curve and experienced each of anyone's
four points, I don't agree or I don't understand this one point on good
housekeeping.  Allowing macros to declare the global macro variables
they set  hides complexity and groups functionality for easier
maintenance and improved readability.

cur

--
Curt Seeliger, Data Ranger
CSC, EPA/WED contractor
541/754-4638
seeliger.curt@epa.gov