comment on

Think about where someone who has never encountered the code before would most likely find and understand the default processing and defaults. To my mind having the strings in the construction code is a pretty reasonable way to do it. The code is clear, concise and easy to maintain without needing any additional explanation.

If the strings are long and span multiple lines using HEREDOCs can make it easier to see how things hang together.

For default handling defined or (//) is your friend.

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

In reply to Re: Good practice for OO module defaults by GrandFather
in thread Good practice for OO module defaults by davies

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks