Comments on: Useless code http://losingfight.com/blog/2007/05/08/useless-code/ because i don't write software for windows Mon, 27 Feb 2012 21:23:01 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Uli Kusterer http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-429 Uli Kusterer Tue, 22 May 2007 09:20:34 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-429 Maybe the programmer just needed a place to set a breakpoint on? This is essentially a no-op, but it still compiles to something. If this is a place where he needs to break often during debugging (i.e. it was some sort of main entry point or bottleneck), he'll be happy if he can just uncomment this thing, put a breakpoint next to it and get debugging. And maybe one programmer put this code there, and another came by, thought: "What's the point of this? I'll comment it out and ask Jeff why he did that!" And that's how it happened. If nobody had to debug this spot recently, it may have just not been uncommented again. I could see dozens of reasons for such a statement, all perfectly valid. Maybe the programmer just needed a place to set a breakpoint on? This is essentially a no-op, but it still compiles to something. If this is a place where he needs to break often during debugging (i.e. it was some sort of main entry point or bottleneck), he’ll be happy if he can just uncomment this thing, put a breakpoint next to it and get debugging.

And maybe one programmer put this code there, and another came by, thought: “What’s the point of this? I’ll comment it out and ask Jeff why he did that!” And that’s how it happened. If nobody had to debug this spot recently, it may have just not been uncommented again.

I could see dozens of reasons for such a statement, all perfectly valid.

]]> By: Jonathan Grynspan http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-428 Jonathan Grynspan Sat, 12 May 2007 03:14:50 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-428 It's possible that, at some point in the development cycle, a complex expression was in the place of that "1", as well as in other places. As the program evolved, the expression became obsolete and a clever developer decided to replace all instances with "1" to avoid having to modify logic or redo unit testing. It's a bit of a stretch, but one can hope that the developer was not so blatantly dumb. It’s possible that, at some point in the development cycle, a complex expression was in the place of that “1″, as well as in other places. As the program evolved, the expression became obsolete and a clever developer decided to replace all instances with “1″ to avoid having to modify logic or redo unit testing.

It’s a bit of a stretch, but one can hope that the developer was not so blatantly dumb.

]]> By: George Sudarkoff http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-427 George Sudarkoff Wed, 09 May 2007 05:28:04 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-427 You want to see HUGE functions? Look at this: http://george.sudarkoff.com/2007/02/_how_many_problems_can.html You want to see HUGE functions? Look at this: http://george.sudarkoff.com/2007/02/_how_many_problems_can.html

]]> By: Joe Goh http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-426 Joe Goh Wed, 09 May 2007 05:23:08 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-426 "Where is there loads of code in a switch-case in the first place?" Oops, should be "Why" instead of "Where". “Where is there loads of code in a switch-case in the first place?”

Oops, should be “Why” instead of “Where”.

]]> By: Joe Goh http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-425 Joe Goh Wed, 09 May 2007 05:21:31 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-425 In my previous full-time job before this startup, i've seen quite a few scary bits of useless code too. else clauses with no code inside. switch-case statements with LOTS of unreachable code following a break statement, which makes you really, really scared. Where is there loads of code in a switch-case in the first place? Ahhh, that's a much longer story for another day. Lots of "legacy functions" that nothing is calling anymore. And these functions are HUGE (more than 150 lines for sure). Life as a maintenance programmer is good. In my previous full-time job before this startup, i’ve seen quite a few scary bits of useless code too.

else clauses with no code inside.

switch-case statements with LOTS of unreachable code following a break statement, which makes you really, really scared. Where is there loads of code in a switch-case in the first place? Ahhh, that’s a much longer story for another day.

Lots of “legacy functions” that nothing is calling anymore. And these functions are HUGE (more than 150 lines for sure).

Life as a maintenance programmer is good.

]]> By: George Sudarkoff http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-424 George Sudarkoff Wed, 09 May 2007 05:02:49 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-424 We all have our own little moments (and idiosyncrasies). Sometimes, especially when you are chasing after a particularly illusive bug, such small reassurances of things still being generally sane might help you not to loose it completely. Or maybe it's a reminder for something. Or a case of careless find and replace. Or a result of some script running. Or this is a custom ASSERT that does more than you think. I mean, who knows? Don't be so quick to judge. :) We all have our own little moments (and idiosyncrasies). Sometimes, especially when you are chasing after a particularly illusive bug, such small reassurances of things still being generally sane might help you not to loose it completely.

Or maybe it’s a reminder for something. Or a case of careless find and replace. Or a result of some script running. Or this is a custom ASSERT that does more than you think. I mean, who knows? Don’t be so quick to judge. :)

]]> By: Joe Goh http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-423 Joe Goh Wed, 09 May 2007 02:34:37 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-423 Ooops, that's right. Serves me right for replying to blogs 10 mins after waking up. :-) Hmm, in that case, I have no idea why he wrote that line. If the original coder is still around, perhaps you should ask him (nicely). Ooops, that’s right. Serves me right for replying to blogs 10 mins after waking up. :-)

Hmm, in that case, I have no idea why he wrote that line. If the original coder is still around, perhaps you should ask him (nicely).

]]> By: Andy http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-422 Andy Wed, 09 May 2007 02:08:20 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-422 Well, ASSERT(1) would _never_ fire, where had he done ASSERT(0), that would fire all the time. And like you said, ASSERTs that fire all the time can be useful (i.e. if you reach a code flow that shouldn't ever be reached). Well, ASSERT(1) would _never_ fire, where had he done ASSERT(0), that would fire all the time.

And like you said, ASSERTs that fire all the time can be useful (i.e. if you reach a code flow that shouldn’t ever be reached).

]]> By: Joe Goh http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-421 Joe Goh Wed, 09 May 2007 01:25:42 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-421 There could be another reason why he chose to do ASSERT(1) - to make sure that assertions are not compiled in the release build, or some other reason where he would want assertions to trigger everytime. Is this ASSERT(1) in the -init method? The good news though is that at least he uses ASSERT(). I've known quiite a few coders in the past who have not even heard of the concept. There could be another reason why he chose to do ASSERT(1) – to make sure that assertions are not compiled in the release build, or some other reason where he would want assertions to trigger everytime. Is this ASSERT(1) in the -init method?

The good news though is that at least he uses ASSERT(). I’ve known quiite a few coders in the past who have not even heard of the concept.

]]> By: Andy http://losingfight.com/blog/2007/05/08/useless-code/comment-page-1/#comment-420 Andy Wed, 09 May 2007 01:07:34 +0000 http://www.losingfight.com/blog/2007/05/08/useless-code/#comment-420 Oh, I have Worse Than Failure (the new name) in my RSS feed. :-) Oh, I have Worse Than Failure (the new name) in my RSS feed. :-)

]]>