Re: One byte bool
Re: One byte bool
- Subject: Re: One byte bool
- From: Patrick Perroud <email@hidden>
- Date: Wed, 15 Mar 2006 10:53:45 +0100
On 15 Mar 2006, at 09:55 , Jerry wrote: On 14 Mar 2006, at 22:35, Ben wrote:
I've never understood why people prefer things like bool, int, or long to the much safer types of unit8, int32, int64, and the like.
The problem I always find is that you have a fantastic choice between uint8, uint8_t, UINT8, u_int8, UInt8, U8, guint8, jsuint8 or whatever name the writers of the libraries you're using have come up with this week and they're all declared in differently-named header files or cause compiler errors because one header file typedefs while another #defines the same symbol . We use several third-party libraries in our app and you can find all of the above, and more, in them. If you're writing cross-platform software you'll also get the wars between Mac and Windows naming conventions. And don't get me started on how people define 64-bit ints....
Well - you still have the obvious solution of not using third party libraries: looks like a blunt statement, but actually this is a serious one - you'll just decide when you want to save time: before or after the product was first released. And if you did decide to go with a third party library, then please don't complain about it: the third parties are still free to implement their own stuff as they most pleased - and the fact you are using it is not binding them to your own practices but yourself to them - so if you couldn't stand it (like I usely do) then don't use it (like I usely don't) ;+)
Best regards
Patrick Perroud
|
_______________________________________________
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