Test::Distribution is probably the most widely used of all the Perl modules that I've developed. It's certainly the only one that I know of that has been mentioned in an O'Reilly book.
Over the last couple of years (mainly ever since my wife and I moved out of the parents and gained the responsibility of maintaining our own household) I haven't been able to give it the attention it needed. I'm hoping that will change over the next few years, but I've hoped that several times in the past too...
I'm interested in people's views on what I should do with T::D. Some ideas:
It'd be really good to hear from people that still use Test::Distribution and would appreciate me coming out from hibernation.
After a lot of neglect on my part, http://cpants.perl.org/ is now working again. Sort of...
There are still a few problems (mostly with Meta.YML stuff), and I have to start the analysis manually on my laptop (which means there won't be automatic updates in the next few weeks, but only when I have some hours of CPU to waste)
The Perl search pulls results from 72 assorted Perl related sites including CPAN and perldoc.perl.org. It tends to work for those questions that you're not even sure where to ask.
Perhaps more useful is the CPAN search which I find often outperforms search.cpan.org. In particular it finds 'one word' module names like CGI or FCGI both of which search.cpan.org currently overlooks.
If you have any suggestions for sites I've missed or other improvements give me a shout.
David Golden on Devel::CheckLib. It's similar to Devel::CheckOS, in that it will let module authors specify dependencies which aren't just other perl modules - if they need, eg, libjpeg, then they can use this module in Makefile.PL / Build.PL to make it a pre-req, and if it's missing then the CPAN testers will SHUT UP ABOUT IT and not annoy the author.
I've been a bit quiet for the past month or so, mostly because projects both at work and home have taken up a lot of my time. One of the home projects has involved creating some report documents in PDF. When first thinking about this, I was looking at PDF::API2, and various other PDF modules, but was struck at how much layout work is put into the code. I don't like having to mix the two, as if I have to change anything in the layout it means changing the code. Reading a recent article on perl.com only reaffirms that. If you're creating a special document, this might work for you, but it doesn't for me.
So djberg96 changed that to use an unsigned int by attaching the U to the end of the number. I think I used to know that.0xff << 24
Additionally, I cast some return values from the XS stuff to (UINT *) to ensure that everything treated them as unsigned ints.0xffU << 24
On behalf of the Parrot team, I'm proud to announce Parrot 0.4.17 "Two for Finching." Parrot (http://parrotcode.org/) is a virtual machine aimed at running all dynamic languages.
Parrot 0.4.17 can be obtained via CPAN (soon), or follow the download instructions at http://parrotcode.org/source.html. For those who would like to develop on Parrot, or help develop Parrot itself, we recommend using Subversion or SVK on the source code repository to get the latest and best Parrot code.
I'm helping David Cantrell with Devel::AssertLib -- particularly with Win32 portability.
I have a branch that passes tests on my Linux and Strawberry Perl platforms, and I've added code that I *think* should work with ActiveState and MSVC, but I don't have that platform set up anywhere.
I'd greatly appreciate if someone(s) would download the branch from my repository, try running tests and let me know what happens:
If it fails and you can patch it to work, that would be wonderful as well.
Thank you very much
One of the implications of the work on Test::Harness 3.0 is that Test::Harness::Straps will no longer exist as part of Test::Harness. For new applications you are encouraged to use TAP::Harness / TAP::Parser. The awkwardness of Straps was one of the reasons to embark on a rewrite of Test::Harness and the new code should make it far easier to write ad-hoc testing applications.
That leaves the question of what should happen to Straps. As Schwern points out it will still work once you have installed Test::Harness 3.0 - but it would be orphaned: installed but unmaintained with no updates available. The solution might be to make an independent release of Test::Harness::Straps. There's a slight danger then that people would continue to use it for new code but the documentation would carry warnings about the inadvisability of that - and ultimately if someone finds it useful, why not?
Let me know what you think.
We're disappointingly white and male - but who knew how damn fine we'd look as a group? Somebody should organise a naked calendar photo shoot next. People would pay lots of money not to see that.