| Re: [AD] unicode.c patch |
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
In reply to Henrik Stokseth (Henrik Stokseth <hstokset@xxxxxxxxxx.
no>):
>i think it would be a good idea to start using the new iso c types. see
>/usr/include/stdint.h to see what i mean. this way we ensure portability
>of code as well. allegro makes too much assumptions about the size of
>int beeing 32bits. on my old borland compiler the size was 16bit. on
>ia64 it might be 64bit. instead of making a workaround for a cvs version
>of gcc wouldn't it be a good idea to actually fix this properly once and
>for all?
Bearing in mind the other posts on this thread, it seems to me that a
rewrite of Allegro's integer handling could have some small advantages.
I am happy to put the time into this rewrite, if it is deemed useful,
and if somebody tells me what to do :-)
We could, for instance, define a set of types:
al_uint32, al_sint16, etc.
which would then be defined in a platform-specific way in a platform-
specific header.
Well, let me know if you want me to do anything. Bye for now,
--
Laurence Withers, lwithers@xxxxxxxxxx
http://www.lwithers.demon.co.uk/
Attachment:
signature.asc
Description: PGP signature
| Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |