LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (October 2002, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 28 Oct 2002 15:29:12 -0000
Reply-To:     "roland.rashleigh-berry" <roland.rashleigh-berry@NTLWORLD.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "roland.rashleigh-berry" <roland.rashleigh-berry@NTLWORLD.COM>
Organization: ntlworld News Service
Subject:      Re: tip v9.1 new macro features

"Fehd, Ronald J. PHPPO" <rjf2@CDC.GOV> wrote in message news:9D17D648E4EBD311AD45009027D0DF93050021E5@MCDC-ATL-64... > a little birdie chirpeth: > > > The %IN operator has been postponed to V9.1, or later. > i.e.: %IF &VAR %IN(A B C) %THEN > > > a note will be issued when a macro is named IN. > > i.e. %MACRO IN(...); > Heads up! Dale!

I don't think this is possible with a macro. It would have to be written into the macro interpreter itself because it would have to keep the knowledge of what &VAR was while looking at what was defined to %IN(). Any macro you would write would not be aware of what just preceded it in the macro code. How could it possibly pick this up?

You could always do it like this:

%IF %INDEX(%quotelst(A B C),"&VAR") %THEN...

...so long as you use the %quotelst macro here. http://www.sconsig.com/sastips/roland_rashleigh-berry/

If this is not the case then I would be happy to be proved wrong.


Back to: Top of message | Previous page | Main SAS-L page