Re: Resolving conflicting typedefs uint32
Re: Resolving conflicting typedefs uint32
- Subject: Re: Resolving conflicting typedefs uint32
- From: "Clark Cox" <email@hidden>
- Date: Tue, 15 Jul 2008 06:11:57 -0700
On Tue, Jul 15, 2008 at 12:39 AM, <email@hidden> wrote:
>
> <rant> uint32, sint32, uint16, sint16 etc have been in common use for at least as long as I've been programming (14 years) I have frequently seen these types of conflicts with third party sdks and there's really no reason for it. Using uint32 sint16 etc is a really intuitive way to define numbers, much more so than int, short, long etc. I wish they were just made an official part of the C language so we wouldn't run into these types of silly conflicts. </rant>
C already has such types:
uint8_t
uint16_t
uint32_t
uint64_t
int8_t
int16_t
int32_t
int64_t
Now, we just need to get people to stop defining their own :)
--
Clark S. Cox III
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden