One of my pet peeves, as you may already know, is leaving memory leaks in “final” code.
Another one is leaving compiler Hints and Warnings.
When doing a fresh build, there should be no Hints and no Warnings. Period. No excuses!
- I know some organizations that ship production code with thousands of Hints and Warnings…
- Some developers even disable Hints and Warnings in the IDE…
- You may think it’s reasonable to deal with Warnings (up to drastic enforcement by turning them into Errors so it won’t even compile when there’s a Warning) and not bother with Hints…
The other day at work, when working on our components migration from pre-Unicode to XE, I had a very example of a seemingly benign Hint that was in fact a bug in waiting… Continue reading