Re: [Pyobjc-dev] Re: NSAnyEventMask as unsigned?

[Ronald O. <ous...@ci...>]

On 29 okt 2003, at 19:50, Bob Ippolito wrote:

>
> On Oct 29, 2003, at 1:43 PM, Ronald Oussoren wrote:
>
>>
>> On 29 okt 2003, at 19:09, Bob Ippolito wrote:
>>>
>>> In any case, because this is Python, any sort of bit flag or mask 
>>> really needs to treated as if it were unsigned or else bad things 
>>> start happening and warnings get thrown all over the place (or 
>>> probably break in 2.4).
>>
>> There won't be warnings because we create the int/long objects from 
>> C, but things might still break in 2.4.
>
> Before I committed the fix, I got an exception when I used 
> NSAnyEventMask

That's probably because you used NSAnyEventMask as an unsigned, and 
PyObjC doesn't like that. That has nothing to do with the int/long 
integration process (e.g. the warning you get when typing 0xFFFFFFFF in 
a python script).

I'm currently updating the code generator script to detect 'Mask' 
values and convert those as 'unsigned int' values. That should take 
care of this problem.

Ronald