http://www.perlmonks.org?node_id=239942


in reply to There's a level in Hell reserved for ________

  • ... people who don't check the result of open()
  • ... people who
    indent_the_arguments_of_long_functions( like, this, you, morons );
  • ... people who write
    open F, ">$tmp"; print F @a; print F $new_item; close F; open F, "<$tmp"; @a = <F>; close F;
    because they don't know about the push() operator.
    (Yes, I've seen that in real production code!)
  • ... people who use any Matt Wright script.
  • ... people who think Ruby is better, by any measure, than Perl.
  • ... people who don't understand why it never made sense for Perl to have a switch statement.
  • ... anyone who thinks code embedded in data is better than data embedded in code; and similarly,
  • ... anyone who thinks GUIs are (or can be) as powerful as command-line interfaces.

    jdporter
    The 6th Rule of Perl Club is -- There is no Rule #6.

  • Replies are listed 'Best First'.
    Re^2: There's a level in Hell reserved for ________
    by Aristotle (Chancellor) on Mar 03, 2003 at 04:54 UTC
      indent_the_arguments_of_long_functions( like, this, you, morons );
      ++ for that one alone. Thank goodness for Perltidy.
      open F, ">$tmp"; print F @a; print F $new_item; close F; open F, "<$tmp"; @a = <F>; close F;

      Wow, that's worse than what I had to deal with in UBB5.

      And I agree with the point about GUIs, though I feel I have to point out that for simple things they can be far more convenient than the commandline. I'm thinking iTunes here. Of course, it's actually very hard to design a good graphical interface, and the majority of what's around just sucks.

      Makeshifts last the longest.

        Um, doesn't perltidy indent the arguments too? After all, that is the generally accepted style for Perl.
          Might by default (though a quick skim of the POD suggests otherwise), but you can certainly configure it to suit your tastes.
          $ cat .perltidyrc --indent-columns=4 --continuation-indentation=4 --maximum-line-length=80 --entab-leading-whitespace=4 --tabs --paren-tightness=2 --brace-tightness=1 --block-brace-tightness=0 --square-bracket-tightness=1 --nooutdent-long-quotes --indent-spaced-block-comments --outdent-long-comments --closing-side-comments --closing-side-comment-interval=25 --closing-side-comment-list="sub : BEGIN END" --long-block-line-count=4 --maximum-consecutive-blank-lines=2 #--standard-output #--standard-error-output

          Makeshifts last the longest.

          the generally accepted style for Perl??? I think not! Sure, it's a meme that gets around. But it's sucky, and needs to be squashed by anyone and everyone who thinks about it consciously. Put simply, there is no reason to do it that way, and there are good reasons not to do it that way.

          jdporter
          The 6th Rule of Perl Club is -- There is no Rule #6.

    Re: Re: There's a level in Hell reserved for ________
    by Anonymous Monk on Mar 03, 2003 at 06:27 UTC

      people who don't understand why it never made sense for Perl to have a switch statement.

      If this is the case {grin}, why is it the case?

      Why does Switch exist?

      Why is Perl6 going to have Given/When?

        There's also a special place in heaven for those who understand why it makes sense for Perl6 to have given/when.

        jdporter
        The 6th Rule of Perl Club is -- There is no Rule #6.

          OK, I'll bite. What's a given/when and why is it important?

          -Logan
          "What do I want? I'm an American. I want more."

    Re: Re: There's a level in Hell reserved for ________
    by jryan (Vicar) on Mar 06, 2003 at 08:03 UTC
      ...people who
      indent_the_arguments_of_long_functions( like, this, you, morons );

      Oh what's wrong with that! Honestly, some people just don't have an appreciation for code aesthetics! (or 80 character line width restrictions) (-: