The programmer appears to be confusing the 'eq' and '==' operators; the 'eq' operator in Perl is used for string comparison, while == is used for numerical comparison. The result of using '==' on two strings, e.g. "M" == "F" will always be true, in the sense that 0 == 0. The 'eq' operator *can* be used to test whether 1 == 1, but will report that "1.0" does not equal "1".
$ perl -e 'print "M" == "F", "\n";'
Recommend developing a battery of tests using Test::More to verify the author's assumptions.
As you may have heard, it snowed a little bit here in Virginia last week. And before you say, "Oh, those silly Southerners! Four feet of snow is just a sign of spring!" we'd like you hear this true story of a local area man's brush with the snowpocalypse.
Billy was snowed in at home and, like most of us, was passing the time in front of his computer. Yetis are naturally frightened of microprocessors so this was a logical choice.
After updating his Facebook status with details on his dwindling pantry (canned beans, tacbac, and pickle juice) and tweeting "This sucks. #snomg" at least three times, Billy leaned back in his chair to grab his V-Cube--a 7x7x7 cube of Rubiksian frustration--to give it another shot.
Just as he leaned back and reached, a tree fell through his house and crushed his desk and computer. The tree missed him by two feet.
Was the internet punishing Billy for complaining about the snow all week? Did the V-Cube save Billy's life so he'd have a chance at solving it? Or will Billy meet his grisly end after solving the V-Cube and it no longer needs him to fulfill its mission?
Good luck, Billy. And don't bring that V-Cube anywhere near ThinkGeek HQ.
Actual photograph moments after the tree attack. Now what will keep the Yetis away?
Pictured: Home & Office :: Team Fortress 2 Mug
Real Users find the one combination of bizarre input values that shuts down the system for days.