[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Say No to global-by-default
- From: Frank Kastenholz <fkastenholz@...>
- Date: Thu, 5 Jul 2018 14:09:11 -0400
Problem solved :-)
(I wasn’t sure whether _ENV might be special ... thanks)
On Jul 5, 2018, at 2:01 PM, Luiz Henrique de Figueiredo <lhf@tecgraf.puc-rio.br> wrote:
>> One could imagine a mechanism where tables get locked - new keys are not allowed to be added to locked tables, but existing keys could be used in the usual way[
>
> Just set a __newindex metamethod for _ENV that raises an error.
>
- References:
- Say No to global-by-default, Egor Skriptunoff
- Re: Say No to global-by-default, Viacheslav Usov
- Re: Say No to global-by-default, Etiene Dalcol
- Re: Say No to global-by-default, Viacheslav Usov
- Re: Say No to global-by-default, Thijs Schreijer
- Re: Say No to global-by-default, Viacheslav Usov
- Re: Say No to global-by-default, Thijs Schreijer
- Re: Say No to global-by-default, Viacheslav Usov
- Re: Say No to global-by-default, Marc Balmer
- Re: Say No to global-by-default, Viacheslav Usov
- Re: Say No to global-by-default, Dirk Laurie
- Re: Say No to global-by-default, Pierre-Yves Gérardy
- Re: Say No to global-by-default, Dirk Laurie
- Re: Say No to global-by-default, Frank Kastenholz
- Re: Say No to global-by-default, Luiz Henrique de Figueiredo
