The scope of a variable x is the region of the program in which uses of x refers to its declaration. One of the basic reasons of scoping is to keep variables in different parts of program distinct from one another. Since there are only a small number of short variable names, and programmers share habits about naming of variables (e.g., i for an array index), in any program of moderate size the same variable name will be used in multiple different scopes.
Scoping is generally divided into two classes:
Static scoping is also called lexical scoping. In this scoping a variable always refers to its top level environment. This is a property of the program text and unrelated to the run time call stack. Static scoping also makes it much easier to make a modular code as programmer can figure out the scope just by looking at the code. In contrast, dynamic scope requires the programmer to anticipate all possible dynamic contexts.
In most of the programming languages including C, C++ and Java, variables are always statically (or lexically) scoped i.e., binding of a variable can be determined by program text and is independent of the run-time function call stack.
For example, output for the below program is 10, i.e., the value returned by f() is not dependent on who is calling it (Like g() calls it and has a x with value 20). f() always returns the value of global variable x.
To sum up in static scoping the compiler first searches in the current block, then in the surrounding blocks successively and finally in the global variables.
With dynamic scope, a global identifier refers to the identifier associated with the most recent environment, and is uncommon in modern languages. In technical terms, this means that each identifier has a global stack of bindings and the occurrence of a identifier is searched in the most recent binding.
In simpler terms, in dynamic scoping the compiler first searches the current block and then successively all the calling functions.
Output in a a language that uses Dynamic Scoping :
Static Vs Dynamic Scoping
In most of the programming languages static scoping is dominant. This is simply because in static scoping it’s easy to reason about and understand just by looking at code. We can see what variables are in the scope just by looking at the text in the editor.
Dynamic scoping does not care how the code is written, but instead how it executes. Each time a new function is executed, a new scope is pushed onto the stack.
Perl supports both dynamic ans static scoping. Perl’s keyword “my” defines a statically scoped local variable, while the keyword “local” defines dynamically scoped local variable.
This article is contributed by Vineet Joshi. If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above.
- Lex Program to check valid email
- Compiler Design | Transition diagram for Identifiers
- Lex code to count total number of tokens
- Compiler Design | Single pass, Two pass, and Multi pass Compilers
- What’s the connection between Java and Blockchain?
- Step Wise Guide to start with Open Source
- Compiler Design | Construction of LL(1) Parsing Table
- Introduction to ES6
- Lex Program to accept a valid integer and float value
- Enumeration in Scala
- Iterative Letter Combinations of a Phone Number
- What is OAuth (Open Authorization) ?
- Labeling Algorithm in Compiler Design
- Compiler Design | C program to check syntax of 'for' loop