I do it very often.Originally Posted by Matticus
On my C++ days I wasn't shy of overloading these. If a function signature could be partitioned, it would. But often this meant the function was no very well designed to begin with, since if I can overload it with a different set of parameters, very likely the function was trying to do more than one thing. Recognizing this, I would then move to actually break the initial function into more discreet functions. (two refactorings to finally fix something I should have detected from the start is my statistical mode... grr)
I can't recall the last time I wrote a function with too many parameters to fit in a 120 character line. But I often have to deal with those when working with a library or when functions ask for certain types of strings. I never multiline the arguments list. For some reason I can't stand the look of it. It's part of the reason I would try to get rid of the ones I wrote myself. But if a function demands that many arguments, or requires a long string, I prefer to initialize variables and pass in their names anytime it results in a shorter caller.
