Reply to thread

Message: [QUOTE="Keith Thompson, post: 3810923"] Byte and Octet make sense, since they add some actual information (but keep in mind that a byte isn't necessarily an octet, though a given piece of code might be intended only for environments where it is). I suggest that Uint: typedef unsigned int Uint; doesn't add anything useful, and there's no real possiblity that Uint could be defined as anything other than unsigned int. Worse yet, someone might later change the definition to, say, typedef unsigned long Uint; /* ugh! */ which is a sure sign that Uint was the wrong name in the first place. [/QUOTE]