Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

iOS Objective-C for Swift Developers The Objective-C Mindset Classes Continued: Alloc, Init, Memory and More

Clayton Cohn
Clayton Cohn
15,715 Points

Bad practice

Gabe, you imported your header file into another header file which, outside of certain instances such as importing framework headers, can lead to a slew of problems as you undoubtedly know. I think you should make a point of saying that this example is only for educational purposes and that it is not to become a habit. Someone new to Obj-C is likely to assume that the standard practice is to import headers into other headers because they saw you do it and have never been told otherwise. Just a thought, thanks!