Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Just out of the idleness of curiousity, of course :-)
    • The quick version is as follows.

      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 .pm file.
      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 dependencies, so if needed the .pm file can be dropped onto a system by hand, or embedded in other modules.
      6. A Tiny module should use as little memory overhead as possible. This should be at the VERY most 10% of the large module. Ideally it should use less than 100k of memory to load.
      7. While the lack of some features is acceptable, the Tiny module should endeavor to be COMPATIBLE with the larger one wherever possible (to use a similar API, etc).

      That's the rough guidelines...