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 (February 2003, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 21 Feb 2003 10:30:41 -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: tip v9 knot use quotes in comments
Content-type: text/plain; charset=us-ascii

"Fehd, Ronald J. (PHPPO)" <rjf2@CDC.GOV> 'tip'sily pointed out: > 815 +%*let's knot and say we did?!; > 816 +%**PRCSWARN(3); > 817 +%**PTO2SHIP(DATA = &DATA. ,VERB = W3C); > 818 +%**PTO2SHIP(DATA = &DATA. ,VERB = W3C); > 819 + > 820 +%EXIT: > 821 +RUN;%*................................................... iBuild; > %MEND; > WARNING: The quoted string currently being processed > has become more than 262 characters long. > You may have unbalanced quotation marks.

Ah, yes. The joy of the single quote mark inside macro comments.

I believe I whined about this last year, in version 8 code. But the problem is far older than that, going back at least to the early days of version 6, if not long before version 5. I think my example was even more whimsical than Ron's, giving an Art-Carpenter-esque 'job security' snippet:

%* The conversion can't be overlooked ; weight = 2.206*weight; %* Now aren't you glad you did it? ;

Note that, since there are less than 262 characters there, you don't get an error message. Hence your maintenance people will actually think that your code converted the weights. <insert evil laugh here>

I was really hoping this would get fixed, one of these days. I guess this will have to go into version 13.2, along with Alastair's issues... :-)

David -- David Cassell, CSC

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