By "creative" I meant that when you are working on a max set of 16 parameters in postgres, you have to overload the function to take care of a wider set (more than 16) of possible arguments. But the only way for postgres to distinguish between overloaded functions is to make sure that their argument data types are different -- hence the need sometimes to reorder the arguments.
I didn't mean to imply that "creative" porting = bad coding.
