LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (September 2001, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 19 Sep 2001 11:02:43 -0400
Reply-To:     Mike Rhoads <RHOADSM1@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Mike Rhoads <RHOADSM1@WESTAT.COM>
Subject:      Re: macro language enhancement
Comments: To: "rjf2@CDC.GOV" <rjf2@CDC.GOV>
Content-Type: text/plain; charset="iso-8859-1"

But I still think Michael has the right approach. The point is, if you use a macro to dump out the generated macro variable one "word" per line, you don't have to use hex values as separators, nor can I see why you'd want to. You can simply use blank, or whatever else is appropriate for the macro variable's ultimate use, as the SEPARATED BY delimiter, and have the macro do the work of splitting the words onto separate lines for the dump.

Mike Rhoads Westat RhoadsM1@Westat.com

-----Original Message----- From: Fehd, Ronald J. [mailto:rjf2@CDC.GOV] Sent: Wednesday, September 19, 2001 10:00 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: macro language enhancement

> From: Michael Bramley [mailto:bramley.m@PG.COM] > ...after you have created a space-delimited (or otherwise) > macro variable, call > the following macro to pump the result into the log in a > reasonable fashion.

[deleted] %*doesn't work because macro function %scan does not recognize hex value; [deleted]


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