使用SWIG从Lua创建C++对象时，如何强制十六进制字符串匹配std::string类型重载构造函数？

Great question! This is a common pitfall with SWIG's default type conversion logic for Lua, where strings that look like numeric values (including hexadecimal ones starting with 0x) get automatically coerced to integers—hence why your MyObj("0xAB") call is matching the int constructor instead of the string one.

Here are a few reliable solutions to fix this, depending on your preferences:

1. Explicitly construct a std::string in Lua #

If you haven't already, add support for std::string in your SWIG interface file by including the standard string module:

%include <std_string.i>

This exports the std::string type to Lua, letting you explicitly wrap your hex string in a std::string instance when calling the constructor. This removes any ambiguity for SWIG:

-- Now this will reliably call the std::string constructor
works_correctly = MyObj(std.string("0xAB"))

2. Adjust SWIG's type checking priority #

You can override SWIG's default type matching behavior using a %typecheck typemap to prioritize std::string matches over integer conversions for string inputs. Add this to your SWIG interface file before declaring your MyObj class:

%typecheck(SWIG_TYPECHECK_STRING) std::string {
    // Tell SWIG: if the Lua argument is a string, prioritize matching this parameter
    $1 = lua_isstring(L, $input) ? 1 : 0;
}

class MyObj {
public:
    MyObj(int v);
    MyObj(std::string v);
};

This typemap ensures that any string input (including hex-formatted ones) will first be considered for std::string parameters, bypassing the automatic integer coercion. With this in place, your original MyObj("0xAB") call will work as expected without modifying Lua code.

3. Add a const char* constructor to your C++ class #

If you prefer not to tweak SWIG configuration, you can add a lightweight wrapper constructor in your C++ code that accepts const char* and delegates to the existing std::string constructor:

class MyObj {
public:
    MyObj(int v);
    MyObj(std::string v);
    // Delegate to the std::string constructor
    MyObj(const char* v) : MyObj(std::string(v)) {}
};

SWIG tends to prioritize matching raw string inputs to const char* parameters over converting them to integers, so MyObj("0xAB") will now correctly route to your string-based constructor logic.

My top recommendation is option 2—it fixes the root cause at the binding level without requiring changes to either your Lua calling code or your core C++ class interface.

内容的提问来源于stack exchange，提问作者Mahashi