All the Perl that's Practical to Extract and Report
use Perl Log In
Alias (5735)
Let a thousand (well, two) Tiny modules bloom
January should see the release of another two modules in the
After mailing the DateTime mailing list, and looking into using DateTime::LazyInit as a substitute for DateTime::Tiny, it looks like I can't modify it as I need without either violating the integrity of lazy init, or bloating beyond the 100k limit.
So it looks like DateTime::Tiny is going to go ahead.
The second Tiny module to arrive shortly, and the first one written by someone else that has met all of the criteria for the Tiny suffix, will be XML::Tiny.
As I understand it from a quick review of the code (mailed to me for nameing approval), XML::Tiny (link won't work till after uploaded) is an implementation of an XML parser that targets a specific documented "minimal xml" subset of the entire XML spec.
And all in about 30 lines of code and well less than 100k of memory.
I'm excited to see a new member of the family, and I can't wait to try it out.
because that's exactly how much difference there is. :-)
--Larry Wall in <10209@jpl-devvax.JPL.NASA.GOV>
What are the criteria for the "::Tiny" suffix? (Score:1)
Re: (Score:1)
Re: (Score:1)
1. Tiny modules provide a non-complete replacement for large modules in "as little code as possible". "Large" is loosely defined as needing multiple megabytes of memory to load the module (before doing anything).
2. They should provide enough functionality to solve a useful set of use cases.
3. A Tiny module must consist of only one
4. A Tiny module must be pure Perl, and back-compatible to at least 5.005 (preferably 5.004)
5. A Tiny module must have no non-core depende
Re: (Score:1)