Ug :) I really hate that. I see no benefit in spaces both sides of the commas, or breaking the open paren away from the function name. And if you have to break the params across lines, at least balance their lengths :)

some_function(
    some_variable, some_other_variable, 
    and_yet_another_variable, and_one_more_for, luck
);
[download]

That's not so bad for simple (void) calls as, but when you're retrieving data and checking you get something like

if( some_return_value = some_function( 
    some_variable, some_other_variable, 
    and_yet_another_variable, and_one_more_for, 
    luck ) ) {
    // do some stuff here with some_return_value 
} else {
   // report or otherwise handle the error 
}
[download]

It's just a mess.The best I've come up with for this is

if( 
    some_return_value = some_function( 
        some_variable, some_other_variable, 
        and_yet_another_variable, and_one_more_for, luck 
    )
) {
    // do some stuff here with some_return_value 
} 
else {
   // report or otherwise handle the error 
}
[download]

Which ain't great, but is better than most alternatives to my eyes.

And much better still is

if( someRv = fSome( some, oSome, AYAnother, OneMoreFor, luck )) {
    // do some stuff here with someRv 
} 
else {
   // report or otherwise handle the error 
}
[download]

With the point being that whilst ths abbreviated variable names don't immediately make much sense, by the time a programmer has got familiar enough with the code to consider making changes, they will.