Hello Smonff,
David Golden here states:
> Adam Kennedy was annoyed that a config file loader had a huge memory footprint - Config::Tiny was born
Infact in Config::Tiny we can read:
> The *::Tiny family of modules is specifically intended to provide an ultralight alternative to the standard modules.
And finally some rule found at blogs.perl.org
Here are the rules Adam Kennedy originally defined for what ::Tiny mea
+ns:
1-The module should be implemented in "as little code as possible"
2-The module should implement a useful subset of functionality
3-The module should use at least 1/10th the amount of memory overhead,
+ ideally less than 100k
4-The module MUST have no non-core dependencies
5-The module MUST be only one single .pm file
6-The module should be back-compatible to at least 5.004
7-The module should omit functionality rather than implement it incorr
+ectly.
8-If applicable, the module should be compatible with the larger modul
+e.
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
-
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.
|