I'm using Python 2.1 and SWIG 1.3.14.
I used SWIG on a pretty big project and it worked out
fine. I can use all methods of the C++-classes I want.
But after I imported the wrapper-module and it got
compilated into bytecode, and I use it a second time,
so that the bytecode is used, I get wrong
variable-values ( strange values - looks like they're
not initialised, but they are !) for the variables in
the C++-classes. It's nothing wrong with the mechansim
of getting the variables into python, 'cause I print'em
out in the C++ methods.
When deleting the wrapper-bytecode before using the
wrapper (and force it to use the real code) everything
works fine again.
Something wrong with the bytecode ?
Log in to post a comment.