Re: Non-uniqueness of module names
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: Non-uniqueness of module names
- From: Dirk Laurie <dirk.laurie@...>
- Date: 2019年4月18日 20:53:56 +0200
Op Do. 18 Apr. 2019 om 16:52 het Hisham <h@hisham.hm> geskryf:
> It even uses _VERSION as the example of what _not_ to do! :) I
> understand that this can be interpreted as meaning "globals", and for
> a while I thought that was the case. But then I've had to fix other
> people's code in the wild that did not follow the recommendation above
> and used _ENV as a regular *local* variable name in Lua 5.1, and
> stopped working when Lua 5.2 came around.
Using _ENV as a local name is even an idiom nowadays,
- References:
- Non-uniqueness of module names, Dirk Laurie
- Re: Non-uniqueness of module names, Roberto Ierusalimschy
- Re: Non-uniqueness of module names, Abhijit Nandy
- Re: Non-uniqueness of module names, Sean Conner
- Re: Non-uniqueness of module names, Dirk Laurie
- Re: Non-uniqueness of module names, Gerhard Sittig
- Re: Non-uniqueness of module names, Luiz Henrique de Figueiredo
- Re: Non-uniqueness of module names, Dirk Laurie
- Re: Non-uniqueness of module names, Roberto Ierusalimschy
- Re: Non-uniqueness of module names, Hisham