Can’t find it now, but I recall I should avoid using double variables in iPhone coding for (poor) performance reasons? Is this true? Are there any other known problems with some variable types?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can’t find it now, but I recall I should avoid using double variables in iPhone coding for (poor) performance reasons? Is this true? Are there any other known problems with some variable types?
Using
floatordoubleon embedded devices is slow when there is no FPU.About floating point performance on the iPhone, you can have a look at Break That Thumb For Best iPhone Performance and Cranking Up Floating Point Performance To 11: it deals with floating point performance and floating point operations causing the program to switch back and forth between Thumb mode and regular 32-bit mode.
See also Squeezing Every Drop Of Performance Out Of The iPhone.