Date: Thu, 28 Apr 2011 23:36:10 -0700
Reply-To: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Subject: Re: Tracking Macro Versions
Content-Type: text/plain; charset=us-ascii
For complicated macros used by many people, I assign version numbers and print them in the log. The documentation also has a "What Changed" section keyed to version number.
For less complicated stuff, no.
On Apr 28, 2011, at 6:38 PM, Quentin McMullen wrote:
> Hi All,
> Was wondering how people approach tracking version numbers of macros,
> particularly autocall macros.
> When reviewing old code that invokes an autocall macro, it's sometimes
> helpful to know which version of a macro was used. (i.e., when this
> code was run 3 years ago and invoked %ME, was it v3.0 of %ME at that
> time or was it v4.0?).
> Was thinking about doing something like:
> %macro me (x=);
> %local version;
> %let version=3.0;
> %put Executing &sysmacroname version &version;
> %* main stuff;
> %mend me;
> That would write the version to the log every time the macro is
> executed. But that could be a bit too many extra lines to the log for
> some people's taste. It's probably overkill.
> So I was thinking I could check the value of the msglevel system
> option, and only print the lines if the user has specified msglevel=2.
> But wondering if other folks use version numbers for their autocall
> macros, and if they report the version in the log when macros are
> invoked or compiled.
> Kind Regards,