What to do about weblib methods with lots of arguments

Re: What to do about weblib methods with lots of arguments

by Howard Miller -
Number of replies: 0
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Part of me says, with modern IDEs (and even good ol' ctags) who cares. A little yellow box probably pops up telling you what the parameters are.

I just think it's a matter of common sense. These are my random thoughts..

* More classes are a good thing - just to give a namespace if nothing else. I'd quite like to see something like output::select_from_menu(a,b,c) then I know where to find it.
* A small number of parameters in a function does not require things like associative arrays (or objects, same thing different syntax) for parameters surely. Good example - required_param(name,clean_thing)!!
* Once you go beyond some small but arbitrary number of parameters then it becomes confusing, unreadable and error prone. Then is the time to to wrap the function (and it's friends) up in a class and use setter methods for the parameters. Sure, it's more typing but it's clearer by miles.

Just my $00.02 as they say.