Re: [C++-sig] Strange behavior when split modules

Hi, folks... Does anybody had this same problem? I'll make a simple "dummy" class example to reproduce the error. If it is really a bug, this will be a problem for people who may want to handle extensions of a C++ library also in C++, that should also be wrapped to Python. If derived classes remain in different modules, some things get strange. I suppose that it have something related to some local pointer registry. I'll test it and send the case to you. Thanks, [Eric Jardim]