Funny comments....

Liam OHagan

Ever reviewed someone elses code and found some comments that were a little strange or funny?I came across this while looking at some c source for a poker machine... //Made it so that only the players frog goes 'boing', all the other frogs are wearing sneakers //I can't believe I get paid for this... hehe, well I found it amusing... :-D Liam O'Hagan Senior Test Engineer GLI Australia www.gli.com.au

Christian Graus

Here at ViewBuild we leave each other little messages in the comments all the time. Like the third time I had to go back and fix the MRU code ( we implimented it manually for reasons I cannot remember ), I left this behind for those who kept changing the code for reasons of their own: // I am not an unreasonable person, but if anyone, and I mean ANYONE, ever has need to // change the code below and/or put #ifdefs into it, please, please, PLEASE ask me to do it // or leave your name here. // If this code gets changed without a name being placed here, and the MRU or lastfilesaved // stops working as a result, I will compensate by killing everyone, in alphabetical order // of surname. Yes, Ben goes first, even though he doesn't touch the code. This is how // irrational I am feeling on the subject. Christian #include

Michael Dunn

Yeah, if I'm not in a good mood, I'll try to amuse myself with witty comments. Once whilst adding a quick fix to some NAV code, I just returned if an error occured at the last step. The code just reset the last-accessed date/time to a file, and there was nothing to in an error condition, so the last little block of comments went something like: if ( wefailed ) { return; // Don't do anything if an error occured, since there's nothing meaningful we can do anyway, // and there are more important things to worry about in life, like viruses. } Later on someone mentioned that they'd gotten a chuckle out of that one. :-D --Mike-- http://home.inreach.com/mdunn/ Tables, ladders, chairs, OH MY!

Atul Dharne

LOL so now are you alone ;P

Atul Dharne

LOL so now are you alone ;P

Christian Graus

All alone, except for the voices.... ;) Christian #include "std_disclaimer.h"

realJSOP

In 1989, I put an error message into our apps that only came up when there was no error message assigned to the problem: "Shut 'er down Scotty, the system's suckin' mud." Nobody ever knew it was there (except me), and it survived several major updates to all of our software. Then, one day in 1997, a user called tech support asking what the error message meant. We also sprinkled humorous tips in our tip of the day file, like: "Don't run with sissors." "Never play leapfrog with a unicorn." "If you drop your car keys in molten lava, let 'em go, because man, they're gone." (thanks Phil Hartman)

David Wulff

First, we have a policy that if you ask a question about anything in a source file, you must add a dated, named comment stating the question (it helps to resolve problems further down the line). Now, a collegue came up to me a few months ago now, and asked me to approve a change he wanted to make to an internal project we were working on. The comments follow:

// 24/02/01: TMA: What the f*ck does this do?
// 24/02/01: JC: Not sure. It kinda looks like it just increments a
// .. value then returns it.
// 24/02/01: TMA: Any idea why we need this?
// 25/02/01: JC: No. As far as I can see we don't even call this
// .. function.
// 31/02/01: TMA: I have tried searching the project source and the
// .. design doc, but can't find any reference to it.
// 31/02/01: JC: It should be defunct now. I'll ask Dave if we can
// .. kill it.
// 31/02/01: TMA: Ok, I will try building it with it commented out.

And the code in question:

int AddNumbers(int nOne, int nTwo)
{
return (nOne + nTwo);
}

And I wonder why nothing ever gets done! David Wulff dwulff@battleaxesoftware.com

l a u r e n

i saw this: #ifdef _KANJI // speak fricking english!!! #endif made me smile ;) --- "every year we invent better idiot proof systems and every year they invent better idiots"