Making sure something is really true.....

Nathan D Cook

saw this at work today.... if (Status == "something") { randomValue = true; } else { randomValue = true; } That was it. No other code in that if/else statement. :-D

gavindon

there is no doubt that randomValue is definitively true.

Programming is a race between programmers trying to build bigger and better idiot proof programs, and the universe trying to build bigger and better idiots, so far... the universe is winning.

AspDotNetDev

There is undoubtedly another DLL that inspects this DLL's IL to ensure the code has not been tampered with. If it finds that somebody removed the seemingly extraneous if statement, it will cause ThreadAbortExceptions at random intervals. ;P

[

S<T>::f(U) // Out of line.

](http://msdn.microsoft.com/en-us/library/8yk3t00s(v=vs.71).aspx)

gavindon

:laugh:

Programming is a race between programmers trying to build bigger and better idiot proof programs, and the universe trying to build bigger and better idiots, so far... the universe is winning.

BillW33

I am going to guess that one of those blocks should be setting randomValue = false. If so I would prefer this much simplier version: randomValue = status == "something"; However, when I see code like that I have to check everything around it for correct logic. :(

Just because the code works, it doesn't mean that it is good code.

R Erasmus

Setting a random value to true... that is very random.

"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>

Sterling Camden independent consultant

I'll guess that this code has been significantly reorganized and these are the only statements left from a major cutback. Otherwise, we must assume that the author is insane.

Contains coding, but not narcotic.

TorstenFrings

there is an obvious flaw in this code, it should read like:

if (Status == "something")
{
randomValue = true;
}
else if (Status != "something")
{
randomValue = true;
}
else
{
randomValue = true;
}