From: William K. <wil...@gm...> - 2007-09-02 18:19:21
|
> This is a bit similar to this bug here: > > http://sourceforge.net/tracker/index.php?func=detail&aid=1735931&group_id=1645&atid=101645 > . There is also a reproducable test case in there. The problem there is > related to %import, but the symptoms are very similar. > > -Matthias > After looking at the bug and related posts you mention, I agree that it could be the same issue, where swig is getting incomplete type information during parsing that prevents the complete type information from being used later. Although I can reproduce the problem within just a single module, as shown in my original post, I too ran into this issue in a larger project that used multiple modules. It seems like a nasty, order-dependent kind of bug that can show up and disappear, depending on the precise sequence and content of declarations in the module files. Since my Lua code and unit tests rely upon having the correct type information produced by swig, it has pretty much blocked my use of swig in my current project (wrapping the Irrlicht Game Engine). I hope very much that it can be fixed for the 1.32 release. William |