title: Should I strive for either member functions with a single responsibility or minimising the number of member variables?
body: <p>I have a class called <code>SolarPosition</code> that has many member functions. I currently have a member function called <code>CalculateSolarAzimuthAndAltitude</code> which is a prime candidate for refactoring.</p>
  
  <p>I found that the only way to refactor it to <code>CalculateSolarAzimuth</code> and <code>CalculateSolarAltitude</code> was to add an additional ten member variables, as some preliminary calculations are used by both functions.</p>
  
  <p>Should I be happy with a member function with two responsibilities, or are multiple transient member variables a reasonable sacrifice in order to split it up?</p>