I have gone through various articles, but I still do not know why instanceof should not be used. Kindly let me know your thoughts.
I have gone through various articles, but I still do not know why instanceof
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.
I have gone through various articles, but I still do not know why instanceof should not be used. Kindly let me know your thoughts.
I find a need to use instanceof hints at bad design. It’s a sure sign that a big, complex switch-style construct will follow. Most other times I see it used, we should use polymorphism rather than instanceof. See the Strategy pattern. (relevant examples of use)
The only time I find I need to use it is when implementing
equals(Object o).