From: SourceForge.net <no...@so...> - 2009-06-03 14:22:19
|
Bugs item #2800537, was opened at 2009-06-03 10:22 Message generated for change (Tracker Item Submitted) made by portmanteaufu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=2800537&group_id=1645 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lua Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Zack S. (portmanteaufu) Assigned to: Mark Gossage (mgossage) Summary: Member fields in a namespace result in multiple SWIG types Initial Comment: [This is my first bug report, so please let me know if I need to provide further clarification or additional information.] My problem is very similar to this long-closed bug: https://sourceforge.net/tracker/index.php?func=detail&aid=782778&group_id=1645&atid=101645 I have a Lua module that I've created with a very large number of C++ classes. Some of the classes are declared within a namespace, like so: namespace NS1 { class myClass { public: NS2::someDataType memberField; } // end myClass } // end namespace NS1 When the C++ wrapper file is produced, it contains both a "SWIGTYPE_p_NS1__NS2__someDataType" and a "SWIGTYPE_p_NS2__someDataType". All of the wrapper functions for myClass validate their arguments expecting a SWIGTYPE_p__NS2__someDataType instead of a SWIGTYPE_p_NS1__NS2__someDataType and the program fails when I try to call them. I have manually changed the data type in a couple of areas in my generated wrapper file and can now call those functions properly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=2800537&group_id=1645 |