Date: Wed, 11 Dec 2002 17:24:08 +0100
Reply-To: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
Subject: Re: recruiting cheesy, sleasy SAS tricks
Content-Type: text/plain; charset="iso-8859-1"
I have developed several (quite large) macros, which in their turn use
auxiliary macros (e.g. like macro functions) in order to limit (macro) code.
These auxiliary macros generally are contained in files of the names of
those macros, just like (m)any other usual macros, and they may ba called
from any program and any macro. However, if I need just one or a few very
specific auxiliary macros I code them at the end of the calling macro code
within the file of the calling macro code, thus not in separate files. Once
the parent macro has been called the auxiliary macro is available, even from
other macros if desired.
And I have developed macros which in their turn generate (auxiliary) macros
conditionally, though many people consider this bad practice.
Regards - Jim.
Y. (Jim) Groeneveld, MSc IMRO TRAMARKO tel. +31 412 407 070
senior statist./data man. P.O. Box 1 fax. +31 412 407 080
J.Groeneveld@ITGroups.com 5350 AA BERGHEM, NL www.imrotramarko.com
My computer does what I tell it to do; sometimes it says my instructions are
Notice of confidentiality: this e-mail may contain confidential information
intended for the addressed recipient only.
If you have received this e-mail in error please delete this e-mail and
please notify the sender so that proper delivery can be arranged.
> -----Original Message-----
> From: Michael L. Davis [mailto:michael@BASSETTCONSULTING.COM]
> Sent: 10 December 2002 19:56
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: recruiting cheesy, sleasy SAS tricks
> Hello Friends,
> I'd like to do a Coder's Corner presentation at NESUG next
> year on the subject of "Cheesy, Sleasy SAS Tricks". As an
> example, when coding SCL programs, I'm in the habit of
> including the statement:
> rc=rc ;
> to suppress the compiler warning that I'm creating the
> variable rc but not using it.
> I'd welcome additional candidates for the role of "cheesy,
> sleasy tricks". To qualify, they need to be coding
> declarations or other constructions that suppress the literal
> mindedness of SAS or its sometimes over-solicitous manner of
> trying to protect us from ourselves.
> I'll be sure to acknowledge useful contributions, selected or
> otherwise, in the acknowledgement section of the presentation.
> BTW, thanks to all for the help last week with regards to
> reordering the PDV. Unfortunately, the friend for whom I was
> trolling wanted as easy a method as the RETAIN statement.
> The ATTRIB statement was to change the length of a variable
> brought in by a SET statement. So combining the RETAIN and
> ATTRIB statements did not work (the length was not changed by
> the ATTRIB statement).
> - Michael "Mad Doggy" Davis
> Michael L. Davis
> Bassett Consulting Services, Inc.
> North Haven CT 06473-3712
> web: http://www.bassettconsulting.com
> email: firstname.lastname@example.org
> tel: 203-562-0640