Scripting Guide - SAS

212 Programming Methods Chapter 8
Advanced Scoping and Namespaces
Example of Local:a
Sample Script
Delete Symbols();
Local( {d1l1 = 12},
local:f1f1 = Function( {fa1,
fa2},
{fl1 = 99},
local:fa12 = fa1 + fa2;
Local( {d2l1 = 56},
local:l2l2 = 78;
Show( fa12 );
Show( fl1 );
Try( Show( d1l1 ), Write(
"\!n\!n***Error=" || Char(
exception_msg ) || "\!n" ) );
Show Symbols();
);
local:fa12;
);
f1f1( 2, 3 );
);
Log Output
fa12 = 5;
fl1 = 99;
***Error={"Name Unresolved:
d1l1"(1, "d1l1", d1l1)}
// Local
d2l1 = 56;
l2l2 = 78;
// 2 Local
// Local
fa1 = 2;
fa12 = 5;
fa2 = 3;
fl1 = 99;
// 4 Local
// Local
d1l1 = 12;
// 1 Local
// Global
exception_msg = {"Name
Unresolved: d1l1"(1, "d1l1",
d1l1)};
// 1 Global
5
Resolving Named Variable References
When variables are referenced within a JMP script, JMP resolves the storage location of the variable using a
specific set of rules. If the variable is referenced by a qualified name, then the resolution is based on the
specific qualification specification. If the variable is referenced by an unqualified name, the situation is a bit
more complex. JMP looks through a hierarchy of scopes representing the point of execution with the
executing script. This section describes the rules that are used to resolve named variable references.
By default, variable name resolution in JMP 9 and later works the same way as in JMP 8 and earlier,
allowing your current JSL scripts to be executed unchanged. For JMP 9 and later, the difference between