Re: Re: Re: Re^2: There's a level in Hell reserved for _______

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.

Comment on Re: Re: Re: Re^2: There's a level in Hell reserved for ________ Select or Download Code

Replies are listed 'Best First'.
Re^5: There's a level in Hell reserved for ________ by Aristotle (Chancellor) on Mar 15, 2003 at 11:17 UTC
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]
Re: Re: Re: Re: Re^2: There's a level in Hell reserved for ________ by Anonymous Monk on Mar 15, 2003 at 15:25 UTC
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]


Don't ask to ask, just ask
	PerlMonks

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