Attempt to explain lexical scope

Author: Mouq

lib/Language/variables.pod

@@ -336,11 +336,81 @@ There are also two listops that resemble declarators, but act on
 predefined variables:
 
 =for table
-    Listop
-    ======
+    Listop  Effect
+    ======  ======
     temp    Restores a variable's value at the end of scope
     let     Restores a variable's value at the end of scope if the block exists unsuccessfully
 
+=head2 The C<my> Declarator
+
+Declaring a variable with C<my> gives it lexical scope. This means
+that it only exists within the current block. For example:
+
+    {
+        my $foo = "bar";
+        say $foo; # -> "bar"
+    }
+    say $foo; # !!! "Variable '$foo' is not declared"
+
+This dies because C<$foo> is only defined as long as we are in the same scope.
+
+Additionally, lexical scoping means that variables can be temporarily
+redefined in a new scope:
+
+=begin code
+my $location = "outside";
+
+sub outer-location {
+    # Not redefined:
+    say $location;
+}
+
+outer-location; # -> "outside"
+
+sub in-building {
+    my $location = "inside";
+    say $location;
+}
+
+in-building; # -> "inside"
+
+outer-location; # -> "outside"
+=end code
+
+If a variable has been redefined, any code that referenced the outer
+variable will continue to reference the outer variable. So here,
+C<&outer-location> still prints the outer C<$location>:
+
+=begin code
+sub new-location {
+    my $location = "nowhere"
+    outer-location;
+}
+
+new-location; # -> "outside"
+=end code
+
+To make C<new-location()> print C<nowhere>, make C<$location> a
+dynamic variable using L<the * twigil|#The_*_Twigil>.
+
+=head2 The C<our> Declarator
+
+=head2 The C<has> Declarator
+
+=head2 The C<anon> Declarator
+
+=head2 The C<state> Declarator
+
+=head2 The C<state> Declarator
+
+=head2 The C<augment> Declarator
+
+=head2 The C<supersede> Declarator
+
+=head2 The C<temp> Listop
+
+=head2 The C<let> Listop
+
 =head1 Special Variables
 
 =head2 Often-Used Variables