Has anyone some funny comments to share that they wrote or saw in other people's source code? Perhaps this has been covered here in another thread, but a search didnot yield it.

A few of mine :

' did the plugin find any files? if not ..WHAT THE HELL ARE WE DOING HERE

At this point, obviously, the program should not be executing here.

' okay, have there any Temporary files been created?
' If so, obliterate them please

..right before the seek and destroy of temp files.

a = 0 'REMEMBER

Like a god booming in your ear, so you don't forget...

news = u - ch ' if this is minus then we have a problem

Meaning: if this is negative ..

And my VB error code intercepts would almost alway be something like this:

On Error GoTo Hell
<code> 

Hell:
<error handling>

or

On Error GoTo Doctor
<code> 

Doctor:
<error handling>

haha some people in my class had comments like /* awww its 4am and cant get this **** workign!!!! IM TIREED!!!!*/

Windows 2000 source code:

' Do not change tabs to spaces. It f**ks the Build. You WILL be killed.

i've never thought of doing that im gonna give it a go in my next site lol

At the top of a particularly convoluted and otherwise completely uncommented code:
// Abandon all hope, ye who enter here.
I'm in the habit of marking twisty, head-bending sections of code with a comment like:
// here be dragons

Also check out this site for fun windows 2k comments:http://www.kuro5hin.org/story/2004/2/15/71552/7795

Disclaimer: The above were stolen off of some unremembered site

This is great!

I once stuck a lengthly comment to my java instructor about the uselessness of the code we were writing, just to see if she actually read all our code like she claimed she did. Never heard jack about it.

I was trying to get some php script that a friend of mine bought working once and after 3 attempts of running their installer I thought I'd have a look at the code to figure out what was wrong ... and line that said....

// give in this will never work //

so I did

Starlord

I confess to adding a comment to some code once, that was along the lines of

PHP Code:

function fName() {
/* WHAT WAS I THINKING HERE???  Doesn't seem to do anything...Need to check.
   //questionable code
*/
 //code that worked.
} 


After commenting it out, everything worked fine, so who knows what I was thinking??

lol


I remember seeing in some open source project a comment along these lines:

//Yeah, there are more efficient ways to do this. Bite me.

That one gave me a good laugh.

Most irritating thing I ever encountered was someone so enamored with themselves that they actually named the variables after themself. $brian -- I hate you dude.

I usually write things like: "Microsoft is awesome!" in my CSS files. Of course I am kidding.

Visual basic code gives me the chills

Not especially humorous, but I found that using figlets created by Email Effects makes it very fast to locate major sections of long code. Other programmers laugh at it for some reason though. :-\

/*__      __   _ _         _         ___  ___
  \ \    / / _(_) |_ ___  | |_ ___  |   \| _ )
   \ \/\/ / '_| |  _/ -_) |  _/ _ \ | |) | _ \
    \_/\_/|_| |_|\__\___|  \__\___/ |___/|___/ */

lol there's a new application of ascii art. Takes me back to the BBS days

Haha, funny comments often make its way into the code during testing and development but are usually removed when production/finalization rolls around.

Matt

From the original UNIX source:

   /*
    * If the new process paused because it was
    * swapped out, set the stack level to the last call
    * to savu(u_ssav).  This means that the return
    * which is executed immediately after the call to aretu
    * actually returns from the last routine which did
    * the savu.
    *
    * You are not expected to understand this.
    */

lol

' Do not change tabs to spaces. It f**ks the Build. You WILL be killed.

That made me laugh

Originally Posted by zxcvbnm60

Not especially humorous, but I found that using figlets created by Email Effects makes it very fast to locate major sections of long code. Other programmers laugh at it for some reason though. :-\

/*__      __   _ _         _         ___  ___
  \ \    / / _(_) |_ ___  | |_ ___  |   \| _ )
   \ \/\/ / '_| |  _/ -_) |  _/ _ \ | |) | _ \
    \_/\_/|_| |_|\__\___|  \__\___/ |___/|___/ */

That's an awesome idea! When I make errors, I generally write things like

//FSCKED UP HERE! ARE YOU AN IDIOT!?

//This doesn't work....figures.

//I hate PHP! Okay not really.

Originally Posted by jaymack

From the original UNIX source:

   /*
    * If the new process paused because it was
    * swapped out, set the stack level to the last call
    * to savu(u_ssav).  This means that the return
    * which is executed immediately after the call to aretu
    * actually returns from the last routine which did
    * the savu.
    *
    * You are not expected to understand this.
    */

Originally Posted by zxcvbnm60

Not especially humorous, but I found that using figlets created by Email Effects makes it very fast to locate major sections of long code. Other programmers laugh at it for some reason though. :-\

/*__      __   _ _         _         ___  ___
  \ \    / / _(_) |_ ___  | |_ ___  |   \| _ )
   \ \/\/ / '_| |  _/ -_) |  _/ _ \ | |) | _ \
    \_/\_/|_| |_|\__\___|  \__\___/ |___/|___/ */

Nice ones!

Whenever I've had to put in conditional comments to fix for IE, I usually give the section a class name like, "IEsux" or "billgatesisaf*g". I find that there is some catharsis in that.

tim

PHP Code:

/*Executing this code will probably fail.
Understanding this code will probably fail.
Fixing this code will probably fail.
Contacting customer support about this code will result in being rerouted to
India and talking to an 85-year-old grandmother about knitting and curry
recipes...and will probably fail.
Gaining a promotion at your job as a result of your being able to execute,
understand, fix, or contact customer support about this code will probably fail.
Offering my apologies as a developer to you as the consumer about this
horribly hacked code and your inability to get a promotion at work because of
it will not fail; it just won't happen.
Thank you for purchasing our product. For customer support, call 1.800.KNITNOW*/