perl...

[iago]

That's not true at all. My Perl code doesn't look significantly different from my C or PHP code.

[warz]

Either you're not making use of all the nifty Perl features, or you're just used to reading Perl.

[iago]

Of course I'm not making use of the "nifty" features, they tend to make the code ugly/unreadable. I program it in the cleanest way I can.

[warz]

Of course I'm not making use of the "nifty" features, they tend to make the code ugly/unreadable. I program it in the cleanest way I can.

Ugly and unreadable to the untrained eye! They can speed things up if everyone knows what they means. But, there's always the English module if you don't like the whacky unreadable variable names.

[Sidoh]

Even if everyone is familiar with the shortcuts, there's still a fair amount of extra tracing overhead involved when it's used excessively.

[zorm]

Of course I'm not making use of the "nifty" features, they tend to make the code ugly/unreadable. I program it in the cleanest way I can.

I do much the same, since it makes life easy when someone else wants to glance at my code and see what I did. English readable code for the win.

[warz]

wtf...

Code: [Select]

    sub wanted {
        /^\.nfs.*\z/s &&
        (($dev, $ino, $mode, $nlink, $uid, $gid) = lstat($_)) &&
        int(-M _) > 7 &&
        unlink($_)
        ||
        ($nlink || (($dev, $ino, $mode, $nlink, $uid, $gid) = lstat($_))) &&
        $dev < 0 &&
        ($File::Find::prune = 1);
    }
=X

* warz head spins

[zorm]

Thats a pretty good example of why writing *readable* code is a good thing, no matter what language you are using...

[warz]

hehe yeah, it's just the new lines that make that tough to read. it's essentially just a return statement.

[Camel]

It would be a lot less ugly as a try/catch block.