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.
What’s the rationale behind placing #import statements in .m rather than .h files in Objective-C?
Apple examples bundle them in .m file unless object is used in interface declaration (.h), and docs state that this is correct (“In the interface file, you first import any required header files.”)
What’s confusing me is that .h is supposed to define the interface for the implementation, so #import would logically go to .h file instead of .m.
In any source file, you should only #import what you need to make that file valid for compilation. Keep in mind that your headers might be used by other classes, so you want to make them as lightweight as possible. This is also why it’s preferable to use @class for forward declarations of classes other than your superclass.