That being said, it should be noted that it is possible to create non-configurable global properties: fineProperty( this, 'bar', ) // non-configurable by default the binding 'foo' cannot be removed subsequently the binding 'bar' can be removed from the global environment subsequently the names 'foo' and 'bar' are bound to the global environment they cannot be deleted (more specifically, their corresponding bindings cannot be removed from the environment subsequently), whereas global properties created through assignment are configurable. Global variables are non-configurable, i.e. So, global variables are bound before program evaluation, whereas global properties are bound during program evaluation, when the assignment is evaluated. Global variables are statically scoped, whereas global properties are dynamically added to the global environment: foo // => undefined var foo = 1, and a global property created through an assignment, e.g. However, there are two differences between a global variable created using var ,e.g. Now, based on the above information, it would seem that it would be appropriate to use the terms 'global variable' an 'global property' interchangeably, meaning that both terms represent the exact same set of global bindings.

This.foo // accessing the global variable via a property reference Var foo = 1 // creating a global variable This also means that global variables may be accessed via property references: // global code

This.foo = 1 // creating a global propertyįoo // accessing the global property via a direct reference This means that global properties may be accessed via direct references (like variables): // global code The global object serves as the top-level lexical environment (the top of the scope-chain, if you will).

Another word for variable terms