Hi John Davies,
A few points in random order:
- It's recommended to always make an Moo attribute lazy unless there's a good reason for it not to be.
- If your attribute is lazy you can declare a builder sub for it.
- The builder sub can be anywhere, including a module that is basically just a config file (but lives in lib/).
- The value of the default property of an attribute can also be a coderef or sub.
- Most applications grow to need a config system at some point; I place changeable config data in config files as it's easiest to maintain. If you are concerned about directory structures you can make you config directory relative to the library directory.
Hope this helps!
The way forward always starts with a minimal test.
-
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.
|
