Mandatory, Explicit, Environments, for Data Objects ... in a programming language

 This week : 

• - practiced, explicit environment-passing across scopes, in a Lisp
• - read, about region-based memory allocation pattern
• - read, about how error handling is implemented at the CPU level
• - read, about, how "the stack" commonly referred to in language implementations is "just a stack of environmental variables" ( vis-a-vis the "stack overflow" problem )

Noticed :

• - basically all contemporary programming languages including POSIX SCL, C, Lisp, JS/Python/Ruby etc. have an IMPLICIT top-level scope which the programmer doesn't handle explicitly.
• - for example, in JS you can do a (var global.x) but this is sugared so you can just write (var x)
• - for example, in JS you can do (try{}catch{}) but this is also the same species of sugaring under the hood!

TODO : Now I want to write a language where ENV objects are explicitly declared, passed, and destroyed. But I probably won't too soon, as it's not urgent.