If you need to do what this does, it is a great module to use. We have hierarchical topics coming in Slash, and to select the topics, we use this module, and it works great. We heavily customized the template, and used Template Toolkit instead, and it all just works.
This is a cute and very useful module for Mac programmers, translating Mac OS errors between symbols and numbers, providing subroutine constants, and even giving error descriptions. It also includes a command-line program for getting the same data.
I love TT and use it for Slash and other projects. It could be a bit faster -- not merely in the template execution, but just in the process of selecting the right template for execution in the first place -- and the vast, very good, documentation could be easier to navigate.
This is a nice idea for a module. It lets you store your DBI info -- username, password, host, driver -- in a "virtual user" so you can connect a lot more easily. It could use better documentation for what a virtual user is, and how to add/modify virtual users, and how to secure the module.
This is a very nice driver, but needs some cleaning up, some more reliable and simpler builds, and some better compatibility with different mysql client/server versions (that may be more a MySQL issue than a DBD::mysql issue, I don't know).
I would have given this module a 4, because I use and like it quite a bit, but it now supports RSS 2.0, which is a bogus and broken version of RSS designed to kill RSS altogether, and anything that supports RSS 2.0 is supporting that goal by proxy. It's unfortunate.
The name of this module is bad. If the interface is functional, why is it in Regex*:: namespace? If the point is to supply regexes like Regexp::Common, fine, but if the point is to perform a task -- matching for profanity -- there is no reason for it to be in the Regex*:: namespace.
This makes releasing software so incredibly easy. And thanks to recent modularization, it is easily customizable to your own needs.
Once set up (which can take some work, but the more distributions you have, the easier it is, as you copy over all the files you need from one to the other and make slight modifications), to release a distribution -- once you have made all your changes, bumped your module version, checked it all in -- you just type "release". That's it.
It makes the distribution, tests it, checks the manifest and cvs, tags cvs, uploads it to CPAN and SF.net, and then claims/releases the file on those systems. All with one word!
(I've modified my local copy to also send a note to my use.perl.org journal after everything has been uploaded.)