in reply to Re^2: Qualified package variable access ( s/lexical/private/ )
in thread Qualified package variable access
I think we should stop calling my variables "lexical", but rather "private".
Whatever the intrinsic merits of calling them "lexical", we certainly should not call them "private" because that has an established, widely understood meaning which is different from what these variables are. I refer to private members of classes in OO languages such as C++ and Java.
In fact, "lexical" is a very good name for these variables, because the scope (that is, visibility) and lifetime* are both determined by the static lexical context of the code. You can read the code and know exactly where the variable can be seen and used.
* Of course, both of these things can be "escaped" through references; that's beside the point.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Qualified package variable access ( private methods )
by LanX (Saint) on Dec 19, 2020 at 15:55 UTC | |
by jdporter (Paladin) on Dec 21, 2020 at 19:00 UTC | |
by LanX (Saint) on Dec 21, 2020 at 20:36 UTC | |
|
Re^4: Qualified package variable access ( s/lexical/private/ )
by LanX (Saint) on Dec 18, 2020 at 21:55 UTC |