Claudio Valderrama C. wrote:
>>
>> This is surely not right. The reason for different definition is that
>> FB_API_HANDLE has to be 32-bit on all platforms. Therefore on 64-bit
>> platforms (with 64-bit pointers) it is defined as (32-bit) unsigned int.
>> For a consistent definition, uint32_t (or some unsigned 32-bit integer
>> type where stdint.h isn't available) should be used.
>
> Yes, it would be better to stick to integers always so we don't have this
> mess with different types of casts.
>
Integer isn't well defined, so sticking to int32 might be a better
choice. In ancient history, the Cray architecture had a 64 bit
char, 64 bit short, and 64 bit integer.
Regards,
Ann
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEVFirebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
