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*

6
  • I reformatted your example a bit, to help visually clarify it; however, I think there might be a couple points that need to be technically sorted out in your example. Is the ListManager actually the TriggerManager, and should the second of three items being stored, the TriggerManager, instead be a Trigger? Commented Jun 8, 2013 at 5:59
  • Why is the latter option far more maintainable? I'm not an expert by any means, but the former seems like the natural choice for me. Commented Jun 8, 2013 at 16:40
  • @SteveP. Because every time I add another method to one of the classes or change an argument, I'll need to update the other class as well. Commented Jun 8, 2013 at 17:26
  • @MikeG, okay, that makes sense. What exactly do you mean by "getters?" Commented Jun 8, 2013 at 17:30
  • @SteveP. As in "Getters and Setters"? It just means ways of accessing instance variables through methods. stackoverflow.com/questions/1568091/why-use-getters-and-setters Commented Jun 8, 2013 at 17:37