I released a new version of Pod::Readme yesterday. It's a module for "Intelligently generate a README file from POD" by using POD =begin/=end and =for commands to control what parts of a module's POD are included/excluded in the README. For example, you don't need the details of method calls in the README, nor do you need installation instructions in the module's man page.
This is a major rewrite using "modern Perl" that supports the following features:
- Generating a README in various formats such as pla…
Last month, I mentioned that I was rewriting Pod::Readme.
A pre-release has just been uploaded to ="https://metacpan.org/release/RRWO/Pod-Readme-v1.0…
Back in 2005, I wrote Pod::Readme. It languished a bit, and David Precious took over maintainership around 2010.
The core idea for this is that README files contain redundant information that is already in the POD, but not everything in the POD should be in the README (such as the details for individual method calls).
It's recommended in Task::Kensho but I'm not aware of many people using it. The few buildtool plugins that generate README files from POD seem to use plain POD-…
Summary: you can use CatalystX::LeakChecker to check every request in your test suite for memory leaks.
From my blog, here.
A few days ago, I released Const::Exporter to CPAN.
Basically, it's a module that allows you to define a module with exportable constants that:
- can be read-only scalars, arrays, or hashes (as well as the standard constant functions);
- can refer to each other;
- can be grouped into export tags, and added to multiple tags without repeating the value;
- and easily interspersed with POD describing the constants.
A more detailed discussion of it is on my blog /var/www/users/robert_rothenberg/index.html