Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • It is stupid that Perl demands that outer parentheses if other languages, including Perl 6, do just fine without. You are rationalising that "clearly language problem" if you say more punctuation makes it more readable.

    Obligatory CPAN: looks like that subroutine can be replaced with Tie::CPHash.

    • The point is not that "Perl cannot do it", at least to me. The point is that if you want to pick a reason why "Perl sucks"(tm), there are far better reasons to exclaim that than the fact that it chose to have explicit parenthesis on if conditions.

      This is the same tone of things as "Perl sucks because if I have only one statement for an if block, I have to still put code blocks, and then I have a line with just one curly bracket!!!"[1] Excuse the exclamation marks (trying to make it seem realistic, did it work?), but I have really heard people say that...

      Actually, the same co-worker also complained that Perl has lc instead of lowercase. The common thing about all these complaints, at least to me, is that they are nitpicking at something which wasn't (and still isn't) a mistake. It's the intent of the language. Perl can do that, it just decided not to, for the same reason Larry keeps explaining why he wants a code block even for a single if. It's not that Perl can't change lc to lowercase or to_lowercase_letter_instead_of_the_first_parameter_of_this_function_here. It's because Perl (and perhaps I should say Larry) decided not to.

      I don't know if I explained myself well, sometimes I don't seem to.


      if ( CONDITION ) {
          ... CODE ...