Using POD as the basis of documentation for Perl projects is the usual way to do. There are many modules available to convert POD into several formats. However, I was not able to find a module that creates a single PDF file from all the documentation available for e.g. a single project. Typically a series of PDF files are the result of a conversion. Combining these files and creating a hierarchical outline can be hard work.
As a simple aid, we peeked into pod2pdf and wrote a little wrapper around it in order to handle many files and create the outline. Well, this solution is not rock solid, as we rely on its internals but at least it is short and usually creating PDFs is not mission-critical.
Maybe some parts can still be improved, but for people interested, here is my first try: https://gist.github.com/2277444. Feedback welcome!
CPAN Testers has now been running for nearly 13 years. In that time we have been supported mostly by the community and some very thoughtful individuals, to whom we owe a massive thank you. Ten years ago we were submitting less than 1,000 reports (March 2002) each month, 5 years ago we reached a new high with just under 25,000 reports (March 2007) submitted. In the last year it is no longer unusual to see 1 million reports (August 2011) submissions in a single month. Regular readers of this blog will be well aware of how successful CPAN Testers has become, and how much data we store, as we sped past 20 million reports in February 2012.
Chris Prather will be giving a talk at YAPC::NA 2012 described as:
Most Perl developers are employed by large corporations, but many dream of what it would be like to strike out on their own. Tamarou is a company that has done just that, and we’re here to tell the tale of what it’s like.
It’s been a wild ride so far, and we’ll discuss the illicit details of what we’ve learned over the last two years, and what we probably should have learned.
[From the YAPC::NA Blog.]
Frankfurt am Main is relatively close to the center of Germany.
Größere Karte anzeigen
The ways to reach it are
If you come to YAPC::Europe from somewhat abroad, taking an airplane to Frankfurt Airport (IATA code "FRA") is the recommended way of getting to Frankfurt. It is the central hub of Lufthansa / Star Alliance and serviced by many other airlines as well. The airport is about 30 minutes away from the city center by train. Another airport , somewhat misleadingly named Frankfurt-Hahn Airport is located at almost equal distance from Frankfurt am Main and Luxemburg, but is serviced by airlines that try to avoid the landing fees at Frankfurt Airport. A bus dives from there to Frankfurt Central Station ("Hauptbahnhof") in about two hours.
We’d like to thank our sponsors for stepping up to support us. We really couldn’t do this without their support.
You too could sponsor YAPC.
[From the YAPC::NA Blog.]
Last night over dinner I had a discussion with Miyagawa about what Devel::Cover could steal from Ruby. He mentioned a Ruby backend which uses Vim signs to show coverage information.
So today I shamelessly stole it and produced a basic version for Devel::Cover.
Devel::Cover has more coverage criteria, so extra work will be required to provide this information, but the report seems useful for now. To use it run
$ cover -report vim
and then in vim:
I'd be happy to get bug reports, feature requests, patches or even pull requests against the repository. And if anyone would like to take this idea and produce a backend for emacs or any other editor, please do so.
This has just been released in Devel::Cover 0.84. This is the second Devel::Cover release I have made at the QA hackathon in Paris this weekend. Many, many thanks to all the organisers, sponsors and participants.
After my previous announcement of DB::Color, I've not had much time to work on it. I eventually disabled it on my box because it was broken on many common cases. Thanks to the Paris Perl QA Hackathon, I've solved a few nasty bugs and now I'm happily using it to debug Perl.
There are some caveats.
Syntax highlighting is slow and is broken in a few edge cases. To get around the first issue, I have naïve caching of syntax highlighted files (change the files and the MD5 sum differs and you get a new cache). Any cached file not used in the last 30 days is deleted.
The broken syntax highlighting has resulted in several bug reports for Syntax::Highlight::Engine::Kate.
My favorite bit (cough) with how I replace lines of code with the syntax highlighted versions is this:
Read that last comment. That's the sort of subtle issues that keep tripping me up while I write this. The latest release is on Github and will shortly hit CPAN.
You're wrong! How does it feel to be wrong? I've never been and you look like someone who would know!