title: Is it good programming pracitce to assign Singleton to variables across multiple classes
body: <p>In my app I'm using singleton class (as sharedInstance). Of course I need to use data that is stored in that singleton in multiple classes (view controllers).
  Because writing </p>
  
  <p><code>[[[SingletonClass sharedInstance] arrayWithData] count]</code> or </p>
  
  <p><code>[[[SingletonClass sharedIntanse] arrayWithData] objectAtIndex:index]</code> or some other methods that you use on array is not comfortable I thought to, in the begining of lifecycle of non-singleton class, assign property (strong, nonatomic) of that non-singleton class to have the same address as SingletonClass.</p>
  
  <p><code>self.arrayPropertyOfOtherClassOne = [[SingletonClass sharedInstance] arrayWithData]</code>
  and in some other class</p>
  
  <p><code>self.arrayPropertyOfOtherClassTwo = [[SingletonClass sharedInstance] arrayWithData]</code></p>
  
  <p>Is it good programming practice?</p>
  
  <p>In my opinion there is nothing bad with it. Properties will point to the same address as property in Singleton and after non-singleton class will be destroyed also properties that where pointing to singleton so Reference Count = Refrence count - 1.</p>
  
  <p>Am I correct?</p>