From: Nitro <ni...@dr...> - 2007-09-01 14:15:52
|
Am 01.09.2007, 02:41 Uhr, schrieb William Knight = <wil...@gm...>: > I've done some additional testing and confirmed that this problem is > language and platform independent. In addition to swig + Lua on Mingw,= = > the > type truncation occurs with swig + Python on GNU/Linux. The problem = > occurs > at compile time, with the truncated type info being produced in the = > wrapper > file: > > ----- truncated type info: > > static swig_type_info _swigt__p_DimTint_t =3D {"_p_DimTint_t", "Dim<in= t > = > *", > 0, 0, (void*)&_wrap_class_Dim_Sl_s32_Sg_, 0}; > > ----- expected type info: > > static swig_type_info _swigt__p_DimTint_t =3D {"_p_DimTint_t", "Dim<in= t > > *|Dim<s32 > *", 0, 0, (void*)&_wrap_class_Dim_Sl_s32_Sg_, 0}; This is a bit similar to this bug here: = http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1735931&gro= up_id=3D1645&atid=3D101645 = . There is also a reproducable test case in there. The problem there is = = related to %import, but the symptoms are very similar. -Matthias |