Large Switch statements: Bad OOP?

by

You may get some benefit out of a Command Pattern.

For OOP, you may be able to collapse several similar commands each into a single class, if the behavior variations are small enough, to avoid a complete class explosion (yeah, I can hear the OOP gurus shrieking about that already). However, if the system is already OOP, and each of the 100+ commands is truly unique, then just make them unique classes and take advantage of inheritance to consolidate the common stuff.

If the system is not OOP, then I wouldn’t add OOP just for this… you can easily use the Command Pattern with a simple dictionary lookup and function pointers, or even dynamically generated function calls based on the command name, depending on the language. Then you can just group logically associated functions into libraries that represent a collection of similar commands to achieve manageable separation. I don’t know if there’s a good term for this kind of implementation… I always think of it as a “dispatcher” style, based on the MVC-approach to handling URLs.

More Related Contents:

  1. Why does C# not provide the C++ style ‘friend’ keyword? [closed]
  2. When should I choose inheritance over an interface when designing C# class libraries? [closed]
  3. Multiple Aggregates / Repositories in one Transaction
  4. A way of casting a base type to a derived type
  5. Factory pattern in C#: How to ensure an object instance can only be created by a factory class?
  6. Why doesn’t generic ICollection implement IReadOnlyCollection in .NET 4.5?
  7. How to capture value OOPS & Generic [closed]
  8. Implement a coin jar in C# [closed]
  9. What is the difference between a field and a property?
  10. Why not inherit from List?
  11. What is the difference between an interface and a class, and why I should use an interface when I can implement the methods directly in the class?
  12. C# Object Pooling Pattern implementation
  13. How can I call the ‘base implementation’ of an overridden virtual method? [duplicate]
  14. Unity singleton manager classes
  15. Why can’t we change access modifier while overriding methods in C#?
  16. Why are private fields private to the type, not the instance?
  17. Singleton by Jon Skeet clarification
  18. How abstraction and encapsulation differ?
  19. How do I target attributes for a record class?
  20. Why can’t I declare C# methods virtual and static?
  21. Merge multiple Lists into one List with LINQ
  22. What is difference between MVC, MVP & MVVM design pattern in terms of coding c#
  23. How to implement SOLID principles into an existing project
  24. The difference between virtual, override, new and sealed override
  25. C# code for association, aggregation, composition
  26. Singleton httpclient vs creating new httpclient request
  27. Is there a much better way to create deep and shallow clones in C#?
  28. getting db connection through singleton class
  29. Entity Framework Specification Pattern Implementation
  30. Why do both the abstract class and interface exist in C#?

Leave a Comment