Home/ Questions/Q 8347999
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T07:33:21+00:00

I was reading this and I am curious about what was meant by increasing

  • 0

I was reading this and I am curious about what was meant by increasing the memory footprint. I am not an expert in any of this, by any means. I actually know very little, other than what I’ve come up with thinking about how systems work. If someone could help clarify my thoughts and correct me where I’m wrong, I would really appreciate it.

I know that by using the proper typedefs, I am future-proofing my code in case apple changes the structure of the typedef and using typedefs shouldn’t affect the processor, since its the compiler’s or preprocessor’s job to basically convert them. But will it actually use any more memory than is necessary, if the typedefs are only used for functions that expect them (and their precision), such as CGRect/CGSize/etc and NSDate functions that ask for those typedefs?

Basically, is there any EXTRA memory being used, given that they are only being used in situations where functions ask for them, rather than using their current counterparts (CGFloat -> float)?

This is for iOS vs OSX, since I know that OSX has both 32bit and 64bit processors and the typedefs are expected.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Think of it this way. Memory footprint often means how much memory you are consuming at any time. If you without any reason use 64 bit values instead of perfectly useful 32 bit ones, then there is some marginal inflation. That said, I’ll bet most of your usage is in automatics and object ivars.

    On iOS now, CGFloat == float.

    I personally ALWAY use CGFloat for anything that might interface with iOS – that is, unless I’m doing some math functions. And for exactly as you said. The other day I had to grab some code on iOS and move it to a Mac app, and it took almost not time (as I use CGFlat, NSInteger, and friends). You will get no conversion warnings (ie moving 64 bit values into 32 bit ones).

    In the future, given the popularity of iOS, its quite likely that there will be processors using 64 bit floating point and integers. Its the nature of progress. If you use the CGFloat and friends, your code will compile without warnings on a universal app the does both 32 and 64 bit.

    • 0