blocks|key|4390169|text|首先，您必须在调用宏之前定义它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390170|其次，只要你事先加载了宏，那么在哪里调用宏并不重要。|4390171|详述你的问题:+autocall库是你的朋友。如果您的SAS管理员不允许您将宏放入autocall库中，您可以像这样附加autocall：|4390172|filename+mymacros+'c:\mysas';+
/*this+defines+the+directory+you+have+stored+your+macros*/

options+sasautos=(sasautos+mymacros)+mautosource;+|code-block|syntax|javascript|4390173|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

First, you must define a macro before it is called.

Second, it doesn't matter where the macro is invoked as long as you have loaded it before-hand. 

To elaborate on your issue: The autocall library is your friend. If you SAS administrator won't allow you to put your macros in the autocall library, you can append the autocall like so:

<pre><code>filename mymacros 'c:\mysas'; 
/*this defines the directory you have stored your macros*/

options sasautos=(sasautos mymacros) mautosource; 
</code></pre>

blocks|key|4390191|text|在调用宏之前，必须先定义它。出于性能原因，最好不要在另一个宏中定义宏--如果这样做，那么每次调用外部宏时都会重新定义它。下面的代码运行良好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390192|%25macro+a;
++%25put+a;
++%25b
%25mend+a;

%25macro+b;
++%25put+b;
++%25c
%25mend+b;

%25macro+c;
++%25put+c;
%25mend+c;

%25*--+%25a+is+main+--*;
%25a
/*+on+log
a
b
c
*/|code-block|syntax|javascript|4390193|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

a macro has to be defined before it is called. for performance reasons, it is best not to define a macro inside another -- if you do so, then it will be re-defined every time you call the outer macro. the following works fine:

<pre><code>%macro a;
 %put a;
 %b
%mend a;

%macro b;
 %put b;
 %c
%mend b;

%macro c;
 %put c;
%mend c;

%*-- %a is main --*;
%a
/* on log
a
b
c
*/
</code></pre>

blocks|key|3543014|text|必须先定义一个宏，然后才能调用它，因此带有"%25+A“的行将需要遵循宏A的定义。其他宏定义的顺序并不重要，只要它们是在调用之前定义的。通常在我的程序中，我会像你所描述的那样设置一个主宏，然后程序的最后一行调用这个宏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3543015|另一个要考虑的选项是设置宏自动调用库，其中包含许多宏的定义。这最适用于可重用的宏，这样您就不必在每个程序中重新定义它们。|3543016|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You must define a macro before it is called, so the line with "%A" would need to follow the definition of macro A. The order of the other macro definitions does not matter, as long as they are defined before they are called. Typically in my programs I set up a main macro like you describe, then the last line of the program calls this macro.

Another option to consider is to set up a macro autocall library, which contains the definitions of many macros. This works best for reusable macros, so that you do not have to redefine them in each program.

blocks|key|3543154|text|SAS中的宏代码有两个方面需要定义:编译的宏代码和宏参数：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3543155|宏代码：|offset|length|style|BOLD|3543156|宏代码本身非常简单，因为当遇到SAS令牌时，%25macro系统开始编译SAS宏，并保持编译，直到它命中%25mend令牌。你可能会遇到的唯一真正的问题是，如果你更新了宏代码，并且在执行之前没有重新编译它-在这种情况下，它仍然会运行它在宏库中的旧版本。通过扩展，如果你试图编译一个宏来调用另一个还没有定义的宏，那么你会得到一个错误。由于这些原因，它们需要按照它们被调用的顺序进行编程(如下例所示：%25level3在%25level2之前，%25level2在%25level1之前)|CODE|3543157|宏变量：定义宏变量时，有两个作用域:全局和局部。一旦定义了全局变量，就可以随时随地访问全局变量。但是，局部变量仅存在于定义了局部变量的宏执行过程中。通过扩展，如果已定义局部变量的宏调用任何其他宏，则仍可访问局部宏变量：|3543158|工作示例：|3543159|在下面的示例中，宏是以逆序定义的，以防止SAS返回明显的宏警告调用。|3543160|下图说明了以下示例中的以下宏的结构：|3543161|%7C-----------------------------%7C
%7CGLOBAL+++++++++++++++++++++++%7C
%7C++%7C------------------------%7C+%7C
%7C++%7CLEVEL1++++++++++++++++++%7C+%7C
%7C++%7C++%7C-------------------%7C+%7C+%7C
%7C++%7C++%7CLEVEL2+++++++++++++%7C+%7C+%7C
%7C++%7C++%7C++%7C--------------%7C+%7C+%7C+%7C
%7C++%7C++%7C++%7C++LEVEL3++++++%7C+%7C+%7C+%7C
%7C++%7C++%7C++%7C--------------%7C+%7C+%7C+%7C
%7C++%7C++%7C-------------------%7C+%7C+%7C
%7C++%7C------------------------%7C+%7C
%7C-----------------------------%7C|code-block|syntax|javascript|3543162|编译嵌套宏：|3543163|+%25macro+level3+;
++%25put+****+START+LEVEL3+****+;
++%25local+G1;
++%25let+G1=Local+;

++%25do+i=1+%25to+2+;
++++%25put+In+the+macro+do+loop+I=&i+;
++%25end+;

++%25put+The+value+of+I+at+level3+is:+&I+;
++%25put+Are+we+accessing+global+or+local+G1+variable+here:+&G1+;

++%25put+****+END+LEVEL3+****;
%25mend+level3+;


+%25macro+level2+;
++%25put+****+START+LEVEL2+****+;
++%25*global+L1+;+*<--+this+would+produce+an+error+because+the+variable+name+has+already+been+added+to+the+local+scope+in+%25level1+;

++%25put+Are+we+accessing+global+or+local+G1+variable+here:+&G1+;
++%25put+Can+we+access+local+variables+here:+&L1+;

++%25level3+;

++%25put+The+value+of+I+in+level2+is:+&I+;
++%25put+****+END+LEVEL2+****;
%25mend+level2+;|3543164|编译顶层宏(依次调用上述两个宏)并运行它：|3543165|%25let+G1=Global;
%25macro+level1+;
++%25put+****+START+LEVEL1+****+;
++%25let+L1=Yes;

++%25put+Are+we+accessing+global+or+local+G1+variable+here:+&G1+;
++%25put+Can+we+access+local+variables+here:+&L1+;

++%25level2+;

++%25put+The+value+of+I+outside+of+the+local+macro+is:+&I+;
++%25put+Are+we+accessing+global+or+local+G1+variable+here:+&G1+;

++%25put+****+END+LEVEL1+****;
%25mend+level1+;
%25level1+;|3543166|查看日志时需要注意的事项：|3543167|3543168|超出%25level3，&I返回宏变量在%25Level3内不存在|unordered-list-item|3543169|的警告，当调用&G1时，它返回存储在%25level3的局部作用域中的值。一旦超出%25level3，该值将返回全局存储的|3543170|的值|3543171|entityMap^0|0|0|4|0|M|6|1E|5|0|0|4|0|0|5|0|G|I|0|0|I|0|0|0|6|0|0|0|L|0|0|0|D|0|0|0|T|0|0|1L|0|0|2|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1L|8|@$D|1M|E|1N|F|J]|$D|1O|E|1P|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1W|8|@$D|1X|E|1Y|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1Z|8|@$D|20|E|21|F|G]]|9|@]|A|$]]|$1|S|3|T|5|U|7|22|8|@]|9|@]|A|$V|W]]|$1|X|3|Y|5|6|7|23|8|@$D|24|E|25|F|G]]|9|@]|A|$]]|$1|Z|3|10|5|U|7|26|8|@]|9|@]|A|$V|W]]|$1|11|3|12|5|6|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|13|3|14|5|U|7|2A|8|@]|9|@]|A|$V|W]]|$1|15|3|16|5|6|7|2B|8|@$D|2C|E|2D|F|G]]|9|@]|A|$]]|$1|17|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|18|3|19|5|1A|7|2F|8|@$D|2G|E|2H|F|G]]|9|@]|A|$]]|$1|1B|3|1C|5|1A|7|2I|8|@$D|2J|E|2K|F|G]]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2L|8|@$D|2M|E|2N|F|G]]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]]|1G|$]]

There are two aspects of macro code in SAS to be defined: the macro code that gets compiled and the macro parameters:

Macro code:

The macro code itself is very simple in that when the <code>%macro</code> token is encountered the SAS system starts to compile a SAS macro and keeps compiling until it hits a <code>%mend</code> token. The only real problems you can come up against is if you updated macro code and don’t recompile it before executing it – in these situations it will still run the old version it has in the macro library. By extension, if you try to compile a macro that calls another macro which hasn’t already been defined then you will get an error. For these reasons, they need to be programmed in the order in which they are called (as shown in below example: %level3 comes before %level2, which comes before %level1)

Macro variables:
When defining macro variables there are two scopes: Global and Local. Once defined, global variables can be accessed anywhere and at any time. However, local variables only exist locally during the execution of the macro in which it has been defined. By extension, if the macro where the local variable has been defined calls any other macros, the local macro variable will still be accessible:

Working Example:

In the following example, the macros are defined in reverse order to prevent SAS returning an Apparent invocation of macro warning.

The below diagram illustrates the structure of the following macros in the following example:

<pre><code>|-----------------------------|
|GLOBAL |
| |------------------------| |
| |LEVEL1 | |
| | |-------------------| | |
| | |LEVEL2 | | |
| | | |--------------| | | |
| | | | LEVEL3 | | | |
| | | |--------------| | | |
| | |-------------------| | |
| |------------------------| |
|-----------------------------|
</code></pre>

Compile the nested macros:

<pre><code> %macro level3 ;
 %put **** START LEVEL3 **** ;
 %local G1;
 %let G1=Local ;

 %do i=1 %to 2 ;
 %put In the macro do loop I=&amp;i ;
 %end ;

 %put The value of I at level3 is: &amp;I ;
 %put Are we accessing global or local G1 variable here: &amp;G1 ;

 %put **** END LEVEL3 ****;
%mend level3 ;


 %macro level2 ;
 %put **** START LEVEL2 **** ;
 %*global L1 ; *&lt;-- this would produce an error because the variable name has already been added to the local scope in %level1 ;

 %put Are we accessing global or local G1 variable here: &amp;G1 ;
 %put Can we access local variables here: &amp;L1 ;

 %level3 ;

 %put The value of I in level2 is: &amp;I ;
 %put **** END LEVEL2 ****;
%mend level2 ;
</code></pre>

Compile the top level macro (which in turn calls the above two macros) and run it:

<pre><code>%let G1=Global;
%macro level1 ;
 %put **** START LEVEL1 **** ;
 %let L1=Yes;

 %put Are we accessing global or local G1 variable here: &amp;G1 ;
 %put Can we access local variables here: &amp;L1 ;

 %level2 ;

 %put The value of I outside of the local macro is: &amp;I ;
 %put Are we accessing global or local G1 variable here: &amp;G1 ;

 %put **** END LEVEL1 ****;
%mend level1 ;
%level1 ;
</code></pre>

Points to note when reviewing the log:

<ul>
<li>Outside of %level3, &amp;I returns a warning that the macro variable does
not exist</li>
<li>Within %level3, when &amp;G1 is called, it returns the value stored in
the local scope of %level3.Once outside of %level3, the value returns
to the value stored globally</li>
</ul>

In my code I have several macros. Macro A is the main macro. Macro A then calls macro B which in turn calls macro C. 

In SAS, do I have to define them in backwards order? In other words, do I have to define macro C first, then macro B, then macro A last? Or does it matter since SAS reads all the code in before it actually hits the command to run the macros? For that matter, can I issue the command to run the macro as the first statement in my code and then define the macros below the command?

Thanks!

SAS: Calling one macro from another...Order of Macro Definitions

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在我的代码中，我有几个宏。宏A是主宏。然后，宏A调用宏B，后者又调用宏C。在SAS中，我必须按倒序定义它们吗？换句话说，我是不是必须先定义宏C，然后定义宏B，最后定义宏A？或者这有什么关系，因为SAS在实际执行命令之前读取所有代码以运行宏？在这个问题上，我可以发出命令来运行宏作为我的代码中的第一个语句，然后在命令下面定义宏吗？谢谢!

问SAS:从宏定义的another...Order中调用一个宏
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SAS:从宏定义的another...Order中调用一个宏EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SAS:从宏定义的another...Order中调用一个宏
EN