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.<br>
<br><div class="gmail_quote">On Wed, Oct 6, 2010 at 6:21 AM, Zac Evans <span dir="ltr"><<a href="mailto:karadoc@gmail.com">karadoc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>This is just a minor point...</div><div><br></div><div>I notice that ENet defines a bunch of int types that are used throughout the library. They are defined like this:</div><div><br></div><div>typedef unsigned char enet_uint8; /**< unsigned 8-bit type */</div>
<div>typedef unsigned short enet_uint16; /**< unsigned 16-bit type */</div><div>typedef unsigned int enet_uint32; /**< unsigned 32-bit type */</div><div><br></div><div>I think it would be better if ENet didn't use these types, and instead used the types defined in <stdint.h>. <br>
</div></blockquote><div> </div></div><br>