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.
As per the title, I’m interested in whether it’s good or bad practice to remove #import <Cocoa/Cocoa.h> from your class headers if the same import is included in your pre-compiled header (.pch).
Apple’s boilerplate classes include the import, but the default project setup in Xcode also imports the Cocoa framework into the default pre-compiled header as well.
It seems to me this is a stylistic question, but I’m interested in opinions and advice.
I usually remove them for files that I know will only be used in the current project. For files that are re-usable (and hence might be used within a project that doesn’t have or or whatever defined in the PCH), I tend to leave them in.