It is one thing to build a perl interface to a database or API, it is another thing to do it well. Doing it well means maintaining your module(s), writing clear documentation, being idiomatic in perl when possible, as well as other things above and beyond programming.
The LDAP::* set of modules fit the criteria of modules that are done well. The documentation is straight forward and the code works. Any idiosyncratic bits should be ascribed to the oddness of LDAP and not these modules.
Ran into a couple bugs using the very basic interface. The documentation is somewhat thin sadly. Not a lot to chose from if you want a dbus module from the CPAN, this module is one of the few which makes it all more crucial that it is in good shape, which it only partly is.
Bug fixing, code refactoring, and a general update are needed to move this module into a more usable tool.
While surely this is good software from a developer and even potentially a user's perspective, it is a lot to manage for the system administrator. It pulls in a lot of dependencies, much more than average, and it pulls in things that one is unlikely to use because many of the dependencies are for Asian languages and locale mangling and the like.
Code re-use is good - but having too many dependencies means you have to shave a lot of yaks just to get your software running and that is a negative.
Allowing signatures, i.e. the specifics of the parameters being passed to a subroutine, is a welcome addition to perl to make it more readable. To have this functionality without using the black magic of Source Filters is even better.
Use this module, and its brother Method::Signatures, if you want cleaner, more readable code.
A useful module to be sure, but perhaps might benefit from a clearer synopsis, an example, and a little bit more thorough documentation. It expects that you have a lot of experience with Moose and Path::Class, which is fine, but it might provide a fuller description to those who arrive here without prior knowledge of those modules. Still an early version so I am certain later versions will be more complete. :)
Requires proper documentation. Upstream Xapian documentation is also pretty spotty. If someone wanted to write an article on how to create, populate and access a Xapian database from perl, that might get published in the Perl Review.
This could be a useful module. However, it lacks all but the most rudimentary documentation. Because things like a synopsis are what most people in the perl community use to judge the usefulness of a module, this module fails the first test since it lacks even a synopsis.
Generally a good module and with decent documentation which got me up and running pretty quickly. There is a bit of a bug in handling From headers, this bug has been in RT for two years now and in debian's BTS for about a year. It would be cool if markov could solve this small problem - then this would be an excellent module.
This is a powerful base class for creating tools to parse logs. The only drawback is that it is really designed and documented for the advanced perl programmer. This in no way takes away from its usefulness but it does mean that people who want to subclass Regexp-Log ought to know what they are doing.
If you do know what you are doing, this module removes a great deal of trial and error with regular expressions and allows one to quickly create a tool to parse the log you have at hand.
Perl is a powerful programming language. This module shows just how powerful. Caveat Emptor; use this if you already are familiar with other IO modules on the CPAN, this one sort of summarizes them and collects them in one place, because it can.
If you are a an experienced perl hacker, this module will save you time and effort. If you are newbie please note that there are clearer, better documented, dare I say more standard interfaces, to Input and Output in perl.
With that said, clearly there is some serious voodoo going on here and judging by the other modules by the same author, this person is a brilliant programmer.
I just read the documentation and I know exactly what this module is for; I can't say that for every module on the CPAN.
This module is for validating the output of your "Test Anything Protocol" script to make sure it adheres to the currently defined specification. Note that the author says it is "experimental", but I am certain if you need to check your TAP, this module will be useful.
This module merely changes the interface to Net::SSH::Perl, it does not extend or replace any of its functionality. It is a new module, and I am sure more work will be done, but it needs to have comensurate documentation when it hits the CPAN so one can quickly find out if this is something one wants to use - this module has nearly no documentation.
This module was written when lvm1 was the current version. lvm2 is now the current version and this module has problems parsing the new format from lvm2, at least under debian. See bug #460604 at bugs.debian.org/cgi-bin/bugreport.cgi...
I have been in touch with Chad so hopefully there will be some movement on the bug front. Chad also says he is re-factoring the code so I look forward to his new initiative!
PS - Gunnar Wolf updated the package for debian which means that if you are using a deb of Linux-LVM your package will be up-to-date. I will forward the patch to RT for the Linux-LVM module so the fix can be incorporated. (June 2, 2008)
First I used this as a "drop-in" replacement for MakeMaker, then I started using it on its own and I am really glad. This means that I can handle dependencies with perl, not with whatever operating system it is going to run on. If someone downloads my module from CPAN, they will be told they need Template and Carp (in my case) without having to wait for the program itself to tell them. Plus it has the cleanest syntax you could hope for.
My concern with this module is that it is not up to date. Qt is now at version 4 and this module only covers Qt 2.0. It looks like development has ceased and this can be a problem since Qt themselves say - "The Qt 4 series is not binary compatible with the 3 series."
I think this would be a great module to develop cross-platform applications, but it has not kept up with Qt and therefor is most likely useless.
I use this module whenever I need to talk to a database. It has excellent documentation, clear examples, and provides a logical interface which makes using it in everyday coding rather easy. I can say that time invested in learning this module is rewarded with an excellent tool and better code.
This is one of those modules that delivers. It does what is says it does with a clear interface, some decent examples, and a perlish way of doing things which means if you are a beginner this is still easy to use. If you are looking for a simple way to graph some info, perhaps for a web site, or for a report, you can do a lot worse that spend a little time with this module.
This can be a great module, it could be really useful. It needs more careful documentation and a more flexible interface.