All the googling I've done so far has turned up things that are very close but just aren't quite cutting it for what I'm trying to do.
Let me describe this in the most basic way possible:
Imagine you have a C++ class
class A { public: int Method(); int Variable; };
Now imagine you instantiate A* Foo;
Now imagine you have a .lua file with this 3 line function:
function Test() local n = Foo:Method(); Foo.Variable = 0; local m = Foo.Variable; end
How can you bind the object A* to lua such that all those things are doable?
Pseudocode-wise, my first attempt went like this, partly from copy pasting examples:
- In a function only called once, regardless of the number of instances of A:
- create newmetatable( MT )
- pushvalue( -1 ) (i dont really get this)
- setfield( -2, "__index" )
- pushcfunction with a static version of Method that unpacks the A* pointer from checkudata
- setfield( -2, "Method" )
- In an init function called for each instance, e.g. Foo:
- create a pointer to Foo with newuserdata
- setmetatable( MT )
- setglobal with Foo to make the name available to lua
- In a test function in main:
- pcall a test function with the 3 lines of .lua mentioned above, by global name
When doing this, Foo:Hide(); successfully called my static function, which successfully unpacked the pointer and called its member Hide().
So far so good for :Method().
Then I tried to support the .Variable access. Everyone seemed to be saying to use metatables again this time overriding __index and __newindex and make them a sort of generic Get/Set, where you support certain keys as valid variable links e.g. if( key == "Variable" ) Variable = val;
This also worked fine.
The problem is trying to put those two things together. As soon as you override __index/__newindex with a getter/setter that works on Variable, the Method() call no longer calls the Method() static function, but goes into the __index function you bound instead.
All of that said, how does one support this seemingly basic combination of use cases?
Actual code snippets would be much more appreciated than purely theoretical chatter.
Reminder: please respond using the basic C API only, not third party stuff.