[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Globals (more ruminations)
- From: Roberto Ierusalimschy <roberto@...>
- Date: Fri, 16 Jul 2010 09:19:51 -0300
> I'm trying to think when I would use this. Under my normal coding
> style, I have no real problem with unintentional global sets
> associated with SETGLOBAL opcodes because I ban SETGLOBAL (plus other
> things) in my lint checks. Perhaps the only small improvement to this
> would be some standardized way (e.g. pragma or comment) to assert in
> source code that "SETGLOBAL opcodes are banned" so that the Lua
> compiler can bark on it without the complication of running an
> external tool (which newbie users wouldn't do).
Exactly. (Moreover, 5.2 will not have SETGLOBAL opcodes anymore ;)
-- Roberto
- References:
- Re: Globals (more ruminations), Roberto Ierusalimschy
- Re: Globals (more ruminations), Geoff Leyland
- Re: Globals (more ruminations), Alexander Gladysh
- Re: Globals (more ruminations), Roberto Ierusalimschy
- Re: Globals (more ruminations), Juri Munkki
- Re: Globals (more ruminations), Roberto Ierusalimschy
- Re: Globals (more ruminations), Patrick Donnelly
- Re: Globals (more ruminations), Roberto Ierusalimschy
- Re: Globals (more ruminations), Edgar Toernig
- Re: Globals (more ruminations), David Manura