Scope in MP Prism

In MP Prism, the scope of the current process determines the scope for resolving the names of variables. See " The Current Process" for a discussion of the current process.

If a command applies to a pset other than the current set, Prism uses the scope of that set's current process.

It is possible that other members of the pset will have different scopes from that of the current process, or that its scope level will not even exist in these processes. In these cases, you receive an error message when you try to issue a command (for example, print or display) that requires a consistent scope. To solve the problem, you can do one of the following:

• Restrict your pset so that it contains only members with the same scope.

• If the current process's scope level does not exist in other processes in the set, you can use the up command to move up its call stack to a point where it has a scope level that does exist in the other processes.

• If different processes in the set have different scopes, you can issue the up and down commands as needed to ensure that they all have the same scope.

Commands such as pset and process that affect scope print the current function when you issue them.