void* problem when addConstructor and addFunction about luabridge3 HOT 5 CLOSED

What do you want to do with the void* in lua land ? Is it an opaque pointer ? I suggest you wrap it in a cfunction compatible lambda and push a lightuserdata in lua land instead

from luabridge3.

It is a database library, the void* is used by blob data type.
such as:

Database db;
db.open()
db.select("xxxx");
while(db.next())
{
  Variant v = db.value(0);
  //now v is a blob type, so we get the data like:
  const void* blobPointer = v.blobValue();
  size_t blobSize = v.blobSize();
}

Now i use a function to do so which is near to what you said. It is work fine, but it looks like not pretty.

from luabridge3.

What i mean is how do you expect it to work on lua side ? if you assign this pointer to lua it needs to be marshalled over a structured type so luabridge can know what it is and how set and retrieve it from the stack. For sure you won't be accessing the blob binary bytes in lua. So create a Blob class that hides the void* and use that to transfer the pointer to lua, by using reference counting you could even safely share ownership (if you can ensure the lifetime of it somehow in c++). Or convert it to a std::vector of std::byte.

If you don't like adding a method, you could use an inline lambda instead of a function to perform the conversion.

from luabridge3.

I added support in #138 for void* and const void* as lightuserdata, it's up to you to make good use of it.

from luabridge3.

I added support in #138 for void* and const void* as lightuserdata, it's up to you to make good use of it.

ok, thanks a lot!!!

from luabridge3.