User Tools

Site Tools


global_and_local_symbol_assignment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
global_and_local_symbol_assignment [2018/12/03 19:48]
lricker
global_and_local_symbol_assignment [2018/12/03 19:49] (current)
lricker
Line 79: Line 79:
   * Local Symbol Tables -- One or more memory-resident data structures within a VMS process which holds the names and values of all //local// variables defined and used by the process. ​ A local symbol table is available automatically at command procedure depth 0 (the command line level) if/when any local variables are defined at that level; in addition, a(nother) local symbol table is created on-the-fly for each command procedural depth >0 reached by subsequent command file invocations (see below).   * Local Symbol Tables -- One or more memory-resident data structures within a VMS process which holds the names and values of all //local// variables defined and used by the process. ​ A local symbol table is available automatically at command procedure depth 0 (the command line level) if/when any local variables are defined at that level; in addition, a(nother) local symbol table is created on-the-fly for each command procedural depth >0 reached by subsequent command file invocations (see below).
  
-  * Command Procedure Depth -- When one command file calls or invokes another one, that called command procedure'​s //depth// is one greater than the one which calls/​invokes it.  By definition, the command line's depth or level is 0 (zero). ​ When you invoke a command file (script) from the command line -- for example: ''​$ @RECURSE''​ (see [[global_and_local_symbol_assignment#​demonstrating_command_procedure_depth|section]] below) -- that command file'​s ​depth or level is 1.  If an executing command file calls yet another one, that called command file'​s ​depth is one greater than the one which calls it.  Command file depth is limited to 31 or less; if an attempt is made to invoke a script at depth 32 or more, DCL generates the error message ''​%DCL-W-STKOVF,​ command procedures too deeply nested - limit to 32 levels''​ (believe me, a depth of 31 is sufficient).+  * Command Procedure Depth -- When one command file calls or invokes another one, that called command procedure'​s //depth// or //level// is one greater than the one which calls/​invokes it.  By definition, the command line's depth is 0 (zero). ​ When you invoke a command file (script) from the command line -- for example: ''​$ @RECURSE''​ (see [[global_and_local_symbol_assignment#​demonstrating_command_procedure_depth|section]] below) -- that command file's level is 1.  If an executing command file calls yet another one, that called command file'​s ​level is one greater than the one which calls it.  Command file depth is limited to 31 or less; if an attempt is made to invoke a script at depth 32 or more, DCL generates the error message ''​%DCL-W-STKOVF,​ command procedures too deeply nested - limit to 32 levels''​ (believe me, a depth of 31 is sufficient).
  
 ==== Demonstrating Command Procedure Depth ==== ==== Demonstrating Command Procedure Depth ====
global_and_local_symbol_assignment.txt ยท Last modified: 2018/12/03 19:49 by lricker