- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
I assume the other wtf is that they don't bother looking at compiler warnings? Or had the one relevant to this one suppressed?I can't imagine this code didn't start issuing warnings when this change occurred. I always make sure my code compiles with no warnings with at least the compiler default warning settings.
Admin
At a long defunct company, "someone" found a list of the executives, and their salaries, left on the copier glass one day.
Several copies of the document were made and distributed. The corporate reaction was fun to watch. "Someone" got away clean.
Admin
That isn't evil. You want true evil?
// Necessary to fix an issue with monthly reconciliation // Do not change! #define double float
That is true evil.
Admin
Source control? Well, that depends. In Git, I can easily impersonate any other colleague. All it takes is to change the name and email in the .gitconfig ;)
Admin
As others have pointed out that's always false and needs to be surrounded by parentheses. Also it will be found out right away if rand() is missing, so this define should be in the file that does have proper include. It would be better is 'true' is actually 'false' in < 1% of the time and 'false' is actually 'true' in < 1% of the time.