Or if size_t isn't appropriate, shouldn't wrapinstance take an unsigned long long or uint64_t? I don't believe unsigned long will work for 64 bit as it's 32 bits on Windows. Should wrapinstance be changed to support all platforms?
On Thu, Feb 6, 2014 at 3:10 PM, Tony Barbieri <[email protected]> wrote: > Hey Ryan, > > Yes, size_t should be used. It looks like in the source code wrapinstance > takes an unsigned long: > > > https://qt.gitorious.org/pyside/shiboken/source/a527dd51e69b80c2d5be3a1d8cd60ab2b2616fa5:shibokenmodule/typesystem_shiboken.xml#L20 > > Maybe we are reading that wrong? Shouldn't wrapinstance be > wrapinstance(size_t, PyObject)? I am not familiar enough with the source > to say for sure. > > Thanks for your reply! > > -tony > > > On Thu, Feb 6, 2014 at 3:04 PM, Ryan Gonzalez <[email protected]> wrote: > >> Well, on 64-bit systems, an unsigned long is equilavent in size to >> size_t(64 bits). Are you sure the Shiboken you compiled was using MSVC >> 64-bit? I believe Visual Studio does 32-bit by default, although I'm not >> sure(haven't worked with VS for a while). >> >> >> On Wed, Feb 5, 2014 at 6:56 PM, Tony Barbieri <[email protected]> wrote: >> >>> Hello! >>> >>> We had submitted a bug awhile back: >>> >>> https://bugreports.qt-project.org/browse/PYSIDE-103 >>> >>> If I find the time I'd like to work on it, but is there any chance >>> someone can take a look at this one? It's bitten us a couple of times. >>> >>> Thanks so much for all the work! >>> >>> -- >>> -tony >>> >>> _______________________________________________ >>> PySide mailing list >>> [email protected] >>> http://lists.qt-project.org/mailman/listinfo/pyside >>> >>> >> >> >> -- >> Ryan >> If anybody ever asks me why I prefer C++ to C, my answer will be simple: >> "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was >> nul-terminated." >> >> > > > -- > -tony > -- -tony
_______________________________________________ PySide mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/pyside
