Global vars ?

[AlleyKat]

In my way I can access to my frame via

local title, M = ...;

in your way I must

local title = ...;
local M = _G[title];

[Lombra]

Originally Posted by AlleyKat In my way I can access to my frame via local title, M = ...; in your way I must local title = ...; local M = _G[title];

Just do this then:

local title, M = ...;
M.frame = CreateFrame("Frame")

[Phanx]

Originally Posted by AlleyKat in your way I must local title = ...; local M = _G[title];

So... adding one line of code is worse, in your mind, than adding multiple extra lines of code and adding the overhead of multiple metatables in your original example?

Originally Posted by AlleyKat Standard metatable functions in frame case we redirect all get and set notfound operations to build-in in build-in we adding frame api and now we don't care what table to use, coz they are same

This is just bad programming. If you want to be able to use two variables to refer to the "same" object, just create one object and point two variables to it. Creating two objects and using metatables to make them act like the same object is just ... I don't even know where you came up with such a convoluted idea. There's no benefit to doing this whatsoever. Then again, there's no benefit to having two variables in the same scope that refer to the "same" object, either, other than purposefully making your code more complicated and difficult to read.

[AlleyKat]

There are no objects in lua, frame is metatable with userdata, where userdata is real frame object, we are not coping userdata, so we are not creating two objects, we are just using object from another instance (another table)

[Phanx]

Yes, but for all practical purposes, they are two different objects in Lua:

local t = {}
local f = CreateFrame("Frame")
print(t == f)

That will print "false" even after all you apply all your pointless hacks. You're completely missing the forest for the trees here.

[AlleyKat]

I said about userdata, not tables