Sorry, 'safe' was a bad choice. I do care because i have compiler warnings. I have started defining macros for each function and thought i better check that they didn't already exist. Thankyou
On 10 August 2010 14:54, Alastair Houghton <alast...@alastairs-place.net> wrote: > On 10 Aug 2010, at 13:42, steven Hooley wrote: > >> Is there a preferred way to use the Math.h functions with CGFloats >> that is 32 and 64 bit safe? > > Why would they be unsafe? (They aren't.) > > It's possible that using the double versions (the ones without the "f" > suffix) is inefficient in 32-bit mode, but in practice you're very unlikely > to notice. If you particularly cared, you could #define some macros for > them, but I doubt it's worthwhile unless you're going to do some heavy-duty > geometry (and in that case, you might find that you want to use double > anyway, for accuracy). > > BTW, <math.h> isn't capitalised; please don't use random upper-case letters > when including header files... it causes grief if your source code is ever > moved somewhere case-sensitive. > >> Should i even be using Math.h functions in Cocoa? > > Why should you not? > > Kind regards, > > Alastair. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
