I sometimes see types named with a suffix of “base”, presumably meaning it forms the parent of one or more sub-types. Is implying the use of inheritance in the type name like this a code smell?
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 sometimes see types named with a suffix of “base”, presumably meaning it forms the parent of one or more sub-types. Is implying the use of inheritance in the type name like this a code smell?
Sometimes the common features of two child classes does not have a natural language equivalent, or the most obvious name would result in a name collision. In such cases I sometimes use a suffix in this manner. I would not consider it a code smell unless it was part of the exported API intended for use by other developers using a library.