3 ms·
Could have been worse: static final int ONE_HUNDRED = 200; // Changed to 50 to optimize
by kibibu 11y ago
Could have been worse:
static final int ONE_HUNDRED = 200; // Changed to 50 to optimize
- danieltillett 11y agoLol - I have to say that I have seen this sort of thing a few times in the past. I actually don't mind this as it is a flashing red light that the code that uses this constant needs to be looked at very, very carefully and rewritten.
- a3n 11y agoI'm still laughing. And it's funny because it's true. And ... the funny could have been eliminated if the named constant had just had a useful name, or been replaced by a function, rather than a passive-aggressive response to a code analyzer or coding standards ("There, I fixed it."). The conflict between the name and its value would have been eliminated, and the comment may have never been written in the first place.