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*
In reply to Re: ::Tiny modules namespace origins
by Discipulus
in thread *::Tiny modules namespace origins
by Smonff
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |