[Swig-devel] SWIG_From_unsigned_SS_int now returns a long

[William S F. <ws...@fu...>]

Hi Stefan

Can you talk us through the motivation for making this change? I see from
http://docs.python.org/library/stdtypes.html that a Python long is 
implemented using a C long. From this I'd say that the changes that 
changed the long typemaps to use a Python long are thus incorrect. Also 
the changes for long long seem unnecessary to always return a Python 
long as they are range checked beforehand to see if they fit into a 
Python int.

William'

On 08/05/12 12:37, Johan Hake wrote:
> Hello!
>
>   From SWIG 2.0.5 or more precis revision 12732 by Stefan Zager,
> SWIG_From_unsigned_SS_int now returns a python long.
>
> This is a (intended/unintended) side effect of letting:
>
>     SWIG_From_unsigned_SS_long
>
> return a python long, because SWIG_From_unsigned_SS_int just calls
> SWIG_From_unsigned_SS_long. Is this a bug? One could argue that an
>
>     unsigned int
>
> should be returned as a python int instead of a python long.
>
> I have some code that breaks because of this change, as our code only
> checks for a python int and not a python long.
>
> Johan
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Swig-devel mailing list
> Swi...@li...
> https://lists.sourceforge.net/lists/listinfo/swig-devel
>