Reply to: Unusual Code Comments

[NickFitz]

// Kick IE to force repaint
element.className = element.className;

Probably a candidate for "Weirdest workaround" as well

[thunderlizard]

I like the ones that say

//To be deleted

So why didn't you?

[FarmerPalmer]

#define FLASH_GORDON 32

[Sysman]

A long time ago in a land far away...

        MOVL    R9, R0                               ; STATUS, R0
        RET                                          ; ONLY HERE FOR THE BEER

The standard was a comment for every line, so even RET got one.

[centurian]

I've often seen:

// increment x
x++;

It's from people who believe that writing comments are what makes good code.

Not quite as blatant as yours, but a favourite of mine is

// Open the connection to the database
dbConnection.Open();

[Muttley08]

Saw this once...

# need another screen refresh, don't know why

this meant another complete set of queries to the database across the WAN - >10 Mb (10 yrs ago), when that was a chunk of WAN and latency with crap queries anyway.

[Zippy]

/// Author: PreviousContractor
/// MadeToWorkBy: Zip's colleague

[VectraMan]

Classic case of commenting what the code does rather than WHY it does it.

I've often seen:

// increment x
x++;

It's from people who believe that writing comments are what makes good code.

[RSoles]

I once came across

PUSH B ;save B&C on stack
PUSH H ;save H&L on stack
LXI B,0 ;load 0 into B&C registers
LXI H,0 ;load 0 into H&L registers

Classic case of commenting what the code does rather than WHY it does it.



Also, on a different contract I had a situation where under a certain set of circumstances the system failed to respond correctly.
looking at the code (nested about five 'if' levels down)

else
{
// really must put some code here
}

[moorfield]

I've seen

Bond jamesBond = new Bond()

a few times on the last two gigs.

It's not funny and it's not clever, whoever you are.

[rootsnall]

I left some witty (?) stuff in some ropey code I left behind while working overseas years ago. I'd forgot all about it until quite a number of years later somebody tapped me on the shoulder at a totally unrelated contract and informed me they were the poor soul who inherited it.

[malvolio]

Not a coding issue as such but many years back a piece of software (called Dracula, would you believe) was used to verify circuit designs on chips - may still be, for all I know. One design failed regularly and it took the experts some time to work out that the designer had drawn a picture of a duck in the middle of the circuit...

[ASB]

Not a comment but I always liked a line of code:-

perform buggery until cock is sore.

[ControlG]

Seen many years ago in a BASIC program

i = 10
REM Just to make sure
i = 10

[Bod]

    /// The point of this is to work around his poor design so that paging will 
    /// work on a mobile control. The main problem is the BindCompany() method, 
    /// which he hoped would be able to do everything. I hope he dies.

	 *
	 * You are not expected to understand this.

and my personal favourite.....

	 * The value returned here has many subtle implications.