Re: Lost information converting decoded value to in32_t

[Riccardo Mottola]

Hi,


Richard Frith-Macdonald wrote:
> My best guess would be either something like NSNotFound (0xffffffff on 32bit 
> 0xffffffffffffffff on 64bit) being encoded, or a negative integer accidentally 
> being encoded as unsigned.
>
> Apart from that it's hard to find integer values which would break the 32bit 
> boundary.

That was also a guess, or I was guessing signed vs unsigned issue!
But when, thanks to Fred, I was able to see that the number was "2" 
debugging had to go to a lower level.

Fun - Thanks to all.

Now, there is yet another warning left when running GWorkspace, but this 
one happens on both 64bit and 32bit, so it is probably different, need 
to know where it comes from too.

Riccardo