in reply to Re: Re (tilly) 1: What you want and perl advocacy gone way wrong
in thread module info
When I have examined my code in the past I find that my average function is about 10 lines. At a guess about 1/3 of those functions are public for whatever package they are in. Public functions get a comment. Function names are descriptive. Most variables are private to a function.
If I cannot find a descriptive name for a 10 line function that gives you some idea why that function exists, that indicates a problem in how I am breaking the problem up.
As with any personal style, it takes getting used to. And no, I don't always do a particulalry good job of it. But I don't think that modularizing less and commenting more would be an improvement.
|
---|
Replies are listed 'Best First'. | |
---|---|
The Purpose of Commenting
by chromatic (Archbishop) on Jan 18, 2001 at 12:04 UTC | |
by I0 (Priest) on Jan 18, 2001 at 20:15 UTC | |
by tilly (Archbishop) on Jan 18, 2001 at 23:28 UTC | |
(Ovid - Yes, but) Re(?): What you want and perl advocacy gone way wrong
by Ovid (Cardinal) on Jan 18, 2001 at 02:36 UTC | |
by tilly (Archbishop) on Jan 18, 2001 at 03:57 UTC |