Date:         Fri, 29 Aug 2008 17:19:57 -0400
Reply-To:     "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Subject:      Re: macro input stack
In-Reply-To:  <082920082100.7938.48B863550005E03800001F02220699849905029A06CE9907@comcast.net>
Content-Type: text/plain; charset=us-ascii

> -----Original Message-----
> From: owner-sas-l@listserv.uga.edu
> [mailto:owner-sas-l@listserv.uga.edu] On Behalf Of iw1junk@comcast.net
> Sent: Friday, August 29, 2008 5:00 PM
> To: SAS(r) Discussion
> Cc: toby dunn; Jack Hamilton
> Subject: Re: Rockville MD
>
> Sumary: Input stack history and other remarks
> #iw-value=1
>
> Jack,
>
> The macro facility dumps the generated code in the "input stack" for
> SAS compilation and execution.  I suspect the term stack is used to
> because this code is executed before the code below the macro call. I
> know, this term does not stack up well with the Fundamental Data
> Structures term stack.
>
> However, as a SAS term it has been in use for a long time.  It appears
> on page 81 and numerous times after that in the 1983 "SAS MAcro
> Language Course Notes" and on page 9 of "SAS Macro Language:
> reference, Version 8" and throughout Chapter 2.  Using the search
> facility at <http://support.sas.com/onlinedoc/913/docMainpage.jsp>
> shows 10 references to the term "input stack".

one needs only spend 49 minutes watching any of
Russ Lavery's most excellent presentations
-- "You did all -that- in PowerPoint!?" --
to know that SAS has several stacks.

and a google of
sas macro input stack

returns
* SGF 2008

http://www2.sas.com/proceedings/forum2008/045-2008.pdf

* SESUG 2006 paper

http://analytics.ncsu.edu/sesug/2006/HW02_06.PDF

and
SAS Macro Language: Reference, Version 8 - Google Books Result

Ron Fehd  the macro maven  CDC Atlanta GA USA RJF2 at cdc dot gov