Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

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

Clayton Cohn
Clayton Cohn
15,715 Points
Posted by 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!