How do I resolve this circular dependency?

Question

I\'m new to iOS development and am running into an issue with my header files. I\'m running into a circular dependency issue with my header files. My application delegate clas

Answer 1

@class is the syntactic approach you're looking for.

Many coders look to avoid this circularity (which couples your classes in two directions, meaning your view controller can only be used in circumstances where the app delegate has that BOOL). There are a few ways you can do this:

• Move the state variable to a singleton
• Have the view controller fetch the value through an interface that the delegate implements
• Key-Value Observing (which your app delegate would configure on your view controller)

For small projects this kind of dependency is probably not really a problem, but as project size grows and the desirability of code reuse grows, clean functional separation becomes more and more valuable.