struct redefinitions . . . . . . . . . . . . . . . . . . . . . . . . 547 42.4 World age and using/import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 42.5 World age capture . . . . 113 julia> module Bar x = 1 foo() = x end; and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace

struct redefinitions . . . . . . . . . . . . . . . . . . . . . . . . 548 42.4 World age and using/import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 42.5 World age capture . . . . 113 julia> module Bar x = 1 foo() = x end; and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace

struct redefinitions . . . . . . . . . . . . . . . . . . . . . . . . 547 42.4 World age and using/import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 42.5 World age capture . . . . 113 julia> module Bar x = 1 foo() = x end; and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace

struct redefinitions . . . . . . . . . . . . . . . . . . . . . . . . 547 42.4 World age and using/import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 42.5 World age capture . . . . 113 julia> module Bar x = 1 foo() = x end; and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace

end; 105CHAPTER 10. SCOPE OF VARIABLES 106 and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace function in the same module. If you want to add methods to a function in another module, you have to import it or use the name qualified with module names. See the section on namespace management. 12.1 Defining

end; 105CHAPTER 10. SCOPE OF VARIABLES 106 and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace function in the same module. If you want to add methods to a function in another module, you have to import it or use the name qualified with module names. See the section on namespace management. 12.1 Defining

end; 111CHAPTER 11. SCOPE OF VARIABLES 112 and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace function in the same module. If you want to add methods to a function in another module, you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining

end; 111CHAPTER 11. SCOPE OF VARIABLES 112 and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace function in the same module. If you want to add methods to a function in another module, you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining

end; 111CHAPTER 11. SCOPE OF VARIABLES 112 and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace function in the same module. If you want to add methods to a function in another module, you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining

113 julia> module Bar x = 1 foo() = x end; and not a x in the scope where foo is used: julia> import .Bar julia> x = -1; julia> Bar.foo() 1 Thus lexical scope means that what a variable in a particular global scope. Modules can introduce variables of other modules into their scope through the using or import statements or through qualified access using the dot-notation, i.e. each module is a so-called namespace function in the same module. If you want to add methods to a function in another module, you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining