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 (March 2002, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Fri, 22 Mar 2002 11:20:17 -0800
Reply-To:   Cassell.David@EPAMAIL.EPA.GOV
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   "David L. Cassell" <Cassell.David@EPAMAIL.EPA.GOV>
Subject:   Re: SAS Coding Standards: comments
Content-type:   text/plain; charset=us-ascii

"Fehd, Ronald J." <rjf2@CDC.GOV> replied [in part]: > I note that an asterisk comment statement shows up in the SAS log. > THEREFORE in order to keep from writing > I'm-not-using-this-statement-and-I-don't-want-to-see-it-in-the-log > statements I -recommend- using macro+asterisk comments.

However, the coder has to watch out for the traps inherent in the %* comment; choice. What happens when your macro contains this choice tidbit?

%* You have to make this conversion, or you'll ruin the later code. ;

ratio = ratio * &GOLDEN_RATIO. ;

%* Now, aren't you glad you listened to me? ;

Oh yeah. The %* does NOT comment out the effect of single quotes from the macro interpreter. SAS will see this as: %* You have to make this conversion, or you followed by something in single quotes, followed by t you glad you listened to me? ; which it will read as the end of the macro comment.

So your code would NOT make that crucial conversion above. Oops.

Maybe I should send this to Art Carpenter. :-)

David -- David Cassell, CSC Cassell.David@epa.gov Senior computing specialist mathematical statistician


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