[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Popularity contest
- From: steve donovan <steve.j.donovan@...>
- Date: Mon, 26 Sep 2011 12:05:19 +0200
On Mon, Sep 26, 2011 at 11:28 AM, liam mail <firstname.lastname@example.org> wrote:
> By this do you mean the removing of _ENV (or a replacement) from being
> set as an upvalue and upvalue table via modifying the core?
_ENV stays the same in every way; but there would be a 'strict
compile' option which requires all variable access to be local.
Assuming then that _ENV always exists as an upvalue, then _ENV.print
is an explicit way to access a 'global'.