1. COT 4600 Operating Systems Fall 2010
Dan C. Marinescu
Office: HEC 439 B
Office hours: Tu-Th 3:30-4:30 PM

2. Lecture 7 – Tuesday September 14, 2010
Last time:
Interpreters.
Communication links.
Today:
Naming;
Use by: value/name
Binding and indirection
Generic naming model
Name mapping algorithms
Comparing names; name discovery
Practical design of naming scheme
Contexts
Name overloading
Next time
UNIX File System
Lecture 7

3. Figure 2.10 from the textbook
Lecture 7

4. 1. Table lookup
Figure 2.11 from the textbook
Lecture 7

5. Single context  ambiguity WORD_PROCESSOR  (INITIALIZE,SPELL_CHECK) SPELL_CHECH (INITIALIZE) (but a different version of it)
Figure 3.1
Lecture 7

6. Two distinct contexts  how does the interpreter choose the context
Two distinct contexts  how does the interpreter choose the context? It needs a basis for the contexts.
Figure 3.3
Lecture 7

7. Add a context reference to each module telling the interpreter which context to use for that module? Not feasible to tinker with someone else’s modules.
Figure 3.4
Lecture 7

8. Have separate contexts but establish a link between them; the link points to the new context for the shared object
Figure 3.5
Lecture 7