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 set my compiler to warn me about methods that could be made static.
These methods are mostly some helpers to do calculations, set attributes on passed objects and so on.
Should I make them static, or is this a sign that my coding style is city (CN)?
Be wary of using static methods for things that you would like to abstract later. Static methods do not support swapping implementations because have a hard link between the consuming class and the implementation class.
That being said, I think there are still places where static methods are appropriate (Utility classes).