Obfuscated Vote Counting Contest

Daniel Horn writes "In a flash of inspiration coming from the Obfuscated C code contest and the current E-voting scandals, I wondered if there shouldn't be a similar code obfuscation contest based on obfuscating voting results, that is, C code that appears correct but does the wrong thing when counting votes. Submit your obfuscated vote-counting code now, and the two winners will be selected on November 2 and will receive a free Vega Strike CD. Obviously incorrect code, however, is not welcome."

Summary of this year's election

[Dancin_Santa]

enum Outcome
{
AMERICAWINS,
AMERICALOSES
}

int main()
{
bool voted = didYouVote();

Outcome o;

switch (voted)
{
case true:
o = AMERICAWINS;
case false:
o = AMERICALOSES;
}
return o;
}

Re:Summary of this year's election

[fossa]

AVP: No matter who wins, we lose.

Re:Summary of this year's election

[Anonymous Coward]

I don't know if you're trying to encourage voting or proposing code for the contest but by leaving out the "break;" in your switch statment I think you've certainly predicted the outcome of this year's elections.

Re:last election

[ezzzD55J]

forgetting strcmp() returns 0 when strings match are we?

Re:my submission

[Peyna]

I fail to trust any poll, because most of them only call during the day, when a certain group of people are home, and another group are likely to not be home. They also do not include a large number of younger voters, who are less likely to respond to a survey, and are more likely to have a cell phone and not a landline phone (which means they won't be called.)

The pollsters "are hoping" that young people continue their streak of not voting much, so their numbers remain accurate.

It's all B.S.

This is pretty much accurate:

[Anonymous Coward]

if(voter.ethnicity != WHITE)
return 0;
if(GetVote(&voter))
{
switch(voter.vote)
{
case BUSH:
case KERRY:
++BusinessAsUsual;
break;
default:
AlertFBI();
}
}

Ken Thompson's compiler hack

[FleaPlus]

The best way to do this would be a variant of Ken Thompson's cc hack, published in ACM back in 1984. Basically the voting code would be pristine, but the compiler itself would be modified to add in "features" at compile time. The compiler also had hooks to add in the trojans while compiling pristine compiler code.

Both compiler and voting application code would appear pristine, with the the actual hack existing only in the compiled code.

Re:You Think You're Funny

[pjt33]

Or more accurately, half of America is sitting right in the middle, and the other two quarters are on the fringes.

Right in the middle of America, maybe. From the perspective of those of us on the other side of the Atlantic, your middle is a good way to the right.