[bndr]

I'm actually the one that wrote the last two nasty parts of code, not the author himself. I'm really sorry that it confused you.

I actually don't remember why I wrote them like that, but I'm pretty sure I had a reason (at least I think I do..)

Again, sorry about that.

[TylerE]

And this is how PHP hell begins.

[ebbv]

Not unique to PHP in any way shape or form.

[TylerE]

Perhaps not, but PHP certainly makes it unusually easy.

[ebbv]

I know this is a popular idea, but it's pretty easy to write terrible code in any language. See: most code.

[TylerE]

Yes, but, in most langauges, this doesn't work

    <?php
    $a = 0;
    $b = 'x';
    var_dump(FALSE == $a);
    var_dump($a == $b);
    var_dump($b == TRUE);
    ?>

This results in

    bool(true)
    bool(true)
    bool(true)

[yareally]

We might as well mention JavaScript's hangups with using == instead of === if we're going to drag out PHP's.

http://stackoverflow.com/questions/359494/does-it-matter-whi...

[babby]

Seriously? (string) x fuzzy equals to (int) 0? Holy crap that is some cancer.

[krapp]

Just tried it... yep.

Though I suppose you could use === but it's still crazy.

[bndr]

Please elaborate. :(

[TylerE]

You wrote nasty code in PHP that you don't clearly understand, and aren't immediately either researching (and then documenting!) why you did what you did, or failing that, recoding for sanity. Once those little hacks calcify it's all down the tubes from there.

[sequoia]

And this is how HN threads get derailed and ruined. Your comment is valueless, please consider deleting it.