Sometimes subroutines turn into large beasts, and there's not much one can do about it. Initialization constructors of complex classes for example. To make the class as configurable as possible, the constructor accepts many parameters. Tk's classes are a good example.
So, there comes a time in a life of a subroutine when I decide to make its arguments named - passing a hash of arg => value pairs into the function. This makes the arguments more manageable, allows to provide default values, etc.
Two questions I have for you:
In reply to named arguments by spurperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |