in reply to Re^2: There's a level in Hell reserved for ________
in thread There's a level in Hell reserved for ________

Um, doesn't perltidy indent the arguments too? After all, that is the generally accepted style for Perl.
  • Comment on Re: Re^2: There's a level in Hell reserved for ________

Replies are listed 'Best First'.
Re^4: There's a level in Hell reserved for ________
by Aristotle (Chancellor) on Mar 03, 2003 at 21:54 UTC
    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

    [download]

    Makeshifts last the longest.

[reply]
[d/l]
Re: Re: Re^2: There's a level in Hell reserved for ________
by jdporter (Paladin) on Mar 11, 2003 at 20:03 UTC
    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.

[reply]
      I've always used this style for args: 
      my_function_call(
                 $arg1,
                 $arg2,
                 $arg3,
                );

      [download]
      And for really long ones that would wrap, I do something like this: 
      My::Module::With::Really::Long::Name::and_function_call(
    $arg1,
    $arg2,
    $arg3,
                                                       );

      [download]
      Keeping each arg on a separate line makes them easy to read and easy to change, in my opinion. It is the most common style I've seen in use by experienced Perl programmers.
[reply]
[d/l]
[select]
        I always write them like so: 
        my_function_call(
    $arg1,
    $arg2,
    $arg3,
);

        [download]
        I indent all blocks, whether they be code, anonymous array/hash constructors, parameter (or other) lists, or anything else in the same way. Makes a lot of sense, if you ask me, when you're nesting calls: 
        my_function_call(
    my_other_function_call(
        $arg1,
        $arg2,
        and_yet_one_more_function_call(
            $arg1,
            $arg2,
            $arg3,
        ),
    ),
    $arg2,
    $arg3,
);

        [download]
        Compare: 
        my_function_call(
                 my_other_function_call(
                                        $arg1,
                                        $arg2,
                                        and_yet_one_more_function_call
+(
                                                                      
+ $arg1,
                                                                      
+ $arg2,
                                                                      
+ $arg3,
                                                                      
+),
                                       ),
                 $arg2,
                 $arg3,
                );

        [download]
        Yuck, if I may say so.

        Makeshifts last the longest.

[reply]
[d/l]
[select]
        I do as Aristotle does. That way if I have to change the line on which the function call is made, I don't have to reindent the arguments.
[reply]

In Section Meditations