Hopefully most of the time. :-)
in reply to When do you function?
Seriously I find that my average function is about 10 lines.
Some are shorter - a lot shorter. A few are much longer.
But that seems to be an average for me.
Here is a list of reasons from chapter 5 of Code Complete
to think about. I won't copy explanations, just the
I have found that all of these benefits still hold in
Perl. Well performance is usually hit a little, but you
are left in a position to optimize where it counts later.
And you shouldn't have non-standard language functions.
But in practice I have noticed portability issues from time
- Reducing complexity
- Avoiding duplicate code
- Limiting effects of changes
- Hiding sequences
- Improving performance (optimize later)
- Making central points of control
- Hiding data structures
- Hiding global data
- Hiding pointer operations
- Promoting code reuse
- Planning for a family of programs
- Making a section of code reusable
- Improving portability
- Isolating complex operations
- Isolating use of non-standard language functions
- Simplifying complicated boolean tests
So while that list doesn't hold perfectly for Perl, it is
still generally on target.
Note that in particular comments explaining what you
intended at one point are not a good substitute for clear
code. Should you change the code later, the comments will
often remain to confuse you. Also deeply nested loops
may not take many lines, but they make it much harder to
separate the forest from the trees.