Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Your argument may or may not have merit, but PDF::API2 is a terrible example to make your point.

    Have you looked in the t/ directory of PDF::API2? Here, I'll save you the time:

    use Test;
    BEGIN { plan tests => 1 }
    use PDF::API2; ok(1);

    With no unit tests, a PASS is meaningless. Only a FAIL has any meaning at all.

    That said, I think PDF::API2 is good code and Fredo has been remarkably responsive in my experience, but my own not-really-competing CAM::PDF [cpan.org] library has unit tests with code coverage over 50% -- not great but infinitely better than PDF::API2.

    • True that, but the sheer percentage of FAILs all of which are on non-prod environments provides an excellent visual example.

    • Also, alas, we're doing PDF creation, and we've implemented pretty much an entire graphic design environment, with box geometry model and a ton of other crazy stuff.

      PDF::API2 is the only thing we've found with enough features and control over the generation of the PDF content.

      The old system this replaced used to use PDFLib, but it's not good enough any longer.

      We'll probably end up contributing patches and improvements to PDF::API2, rather than switching.