Skip to main content
Software Engineering

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.

Required fields*

18
  • 2
    Why would it not? You should edit in your concerns so the answers can be tailored to what you actually want to know, otherwise, you're just going to receive a yes/no answer, which is not very interesting. Commented Feb 13, 2018 at 16:49
  • It's more a question out of curiosity then anything else. I like this solution and don't think I'll change that, I'm just wondering if it's still considered an implementation of the strategy design pattern. Commented Feb 13, 2018 at 16:50
  • If the strategy changes during the lifetime of the Parser object then it is more of a State Pattern. Commented Feb 13, 2018 at 16:59
  • "But the problem is that now I need a new instance of Parser for every entity I load" Why are you concerned about this? Commented Feb 13, 2018 at 17:01
  • @ABittersweetLife not unless it's the IStrategy object that sets the next state (strategy), which is obviously impossible in the second implementation. Also, do you have a source for the claim that a strategy must not be changed during the object's lifetime? I've never heard of that. Commented Feb 13, 2018 at 17:05