I've had issues with "dueling typedefs" as well. One library did it differently than another and where they intersected gcc complained. They ended up being the same at a binary level but it still gave errors.
On Wed, Oct 6, 2010 at 6:21 AM, Zac Evans <[email protected]> wrote: > This is just a minor point... > > I notice that ENet defines a bunch of int types that are used throughout > the library. They are defined like this: > > typedef unsigned char enet_uint8; /**< unsigned 8-bit type */ > typedef unsigned short enet_uint16; /**< unsigned 16-bit type */ > typedef unsigned int enet_uint32; /**< unsigned 32-bit type */ > > I think it would be better if ENet didn't use these types, and instead used > the types defined in <stdint.h>. >
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
