Re: Lua Basics: modules()?

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

• Subject: Re: Lua Basics: modules()?
• From: Tim Gogolin <tgogolin@...>
• Date: 2005年9月12日 14:39:23 -0500

---

local variables can be accessed more efficiently at runtime than named identifier lookups. Locals are found at runtime as an array access (by index), whereas table lookups are a hash table lookup. So this is probably just an attempt to make frequently used function calls execute a little faster.

-- Tim Gogolin
On Sep 12, 2005, at 2:23 PM, William Trenker wrote:

From studying various Lua modules I see that experienced Lua

programmers usually set up a number of local variables that carry the
value of standard library functions, like this:
local assert, error, _G, loadstring, loadfile, _pcall, type, unpack,
xpcall = assert, error, _G, loadstring, loadfile, pcall, type, unpack,
xpcall
What is the point of this? On the surface it appears to be redundant.
 But since it is often used by the experts I'm obviously missing
something important.
Thanks very much,
Bill

---

• Follow-Ups:
  • Re: Lua Basics: modules()?, William Trenker

• References:
  • Lua Basics: modules()?, William Trenker

• Prev by Date: Re: Why can't I do for...in on a table?
• Next by Date: Re: Why can't I do for...in on a table?
• Previous by thread: Lua Basics: modules()?
• Next by thread: Re: Lua Basics: modules()?
• Index(es):
  • Date
  • Thread