Activity Goals

The goals of this activity are:
1. To define the various ways that names can be bound to items such as variables
2. To explain interpreter or compiler binding of types
3. To differentiate between strongly and weakly typed languages
4. To define variable scope
5. To relate scope to a function call stack

The Activity

Model 1: Binding

Questions

1. Can foo be re-assigned at runtime? Would you say that it is statically or dynamically bound to its value? How about x?
2. Do you think this is true of every language?
3. How many bindings are there of the identifier x? If x is staically bound, it must be resolved by the compiler at compile time. How is the correct value obtained at each reference?
4. What would happen if x is re-declared in foo after it has already been declared in languages like C and Java that specify and insist on proper types (these are called strongly typed languages)?

Model 2: Tracking Bindings

Questions

1. What kinds of information are needed to specify a bound symbol?
2. What kind of data structure would enable a dynamic number of bound variables in a routine?
3. What revisions are needed to support additional data types?
4. What revisions are needed to support scope, so that variables of the same name can exist in subroutines?

Model 3: Binding Functions

Questions

1. How can polymorphism work in a statically bound language? How might this differ from a dynamically bound language?

Model 4: Virtual Inheritance

Questions

1. A call to x->Eat(), where x is of type Animal but refers to a Llama, would output what?
2. How would this differ if Eat was not virtual, and implemented in the class Animal?

Submission

I encourage you to submit your answers to the questions (and ask your own questions!) using the Class Activity Questions discussion board. You may also respond to questions or comments made by others, or ask follow-up questions there. Answer any reflective prompt questions in the Reflective Journal section of your OneNote Classroom personal section. You can find the link to the class notebook on the syllabus.