Are there instances where switch(case) is is a good design choice (except for simplicity) over strategy or similar patterns…
Are there instances where switch(case) is is a good design choice (except for simplicity)
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Are there instances where switch(case) is is a good design choice (except for simplicity) over strategy or similar patterns…
Use Switches when you’re testing on values of primitives. (ie. integers or characters).
Use polymorphism when you are choosing between different types.
Examples : Testing whether a character the user has entered is one of ‘a’, ‘b’ or ‘c’ is a job for a switch.
Testing whether the object you’re dealing with is a Dog or Cat is a job for polymorphic dispatch.
In many languages, if you have more complicated values you may not be able to use Switch anyway.