return the combined success
of assertion one
and assertion two
and assertion three
and assertion four
and assertion five
and assertion six
If you're using formatting to line one up, you have to use formatting to line the other up as well. I think I can stop here, as far as this particular example is concerned..
I have nothing against the concept of a guard clause per se, though your example would be much more readable if you emphasize what it is by putting the return in the spotlight and avoiding the ! linenoise:
return unless $fruit;As far as bad memory is concerned, I don't see how my style requires a good one. To the contrary, actually, I tend to be very visually oriented. My code formatting follows that rule - I want to be able to glean the structure of a function's body without having to actually read and grok it all, and indentation carefully follows that motto. Functions should usually not be longer than about 25 lines. Some have to be of course, but those are few and far between. Most of mine tend to be around 15. That's so little you need no memory - you can take the entire function in in a single look. It's beneficial to have as little line noise as possible. Each statement should do as much as possible while being readable at a glance. Repetition is to be avoided. Contrary to intuition, spotting subtle differences in a repeated pattern is difficult - it's easy to detect their presence, but hard to actually make them out. (Have you ever seen much repetition in literature outside of poems?)
Basically I try to write Perl close to how I'd write the same thing in English.
Makeshifts last the longest.
In reply to Re^6: Pattern Matching Query
by Aristotle
in thread Pattern Matching Query
by Elgon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |