Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Definitely nicer than options 1 and 2. This is only a short step away from making use of the strategy design pattern. Commented Jan 28, 2014 at 17:59
  • 4
    This might be appropriate. This might be overkill. Depends on how complex the calculations are. You going to add a MaxPressureFrameStrategy and a MaxPressureFrameStrategyFactory? And it tends to turn Foot into an Anemic Object. Commented Jan 28, 2014 at 21:45
  • Though this is a nice alternative, reversing the dependencies would not work in our case. The foot also has to act as some kind of mediator, as some calculations need to be recalculated if another one changed (due to the user changing a parameter or so). Commented Feb 10, 2014 at 8:34
  • @Bgie: With such dependencies between calculations, I agree with @user116462 that the first option is best.` Commented Feb 10, 2014 at 9:27