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.
  • I believe that in times like these, one is supposed to say: You are wicked and wrong to have broken inside and peeked at the implementation and then relied upon it.

    Let me say that the so-called 'screen-scraping' idea for T::B::T was entirely the author of Test::Builder's idea [perl.org] and uses only documented interfaces. There is no 'breaking inside' or 'peeking' going on. If you can think of any better way to determine if the diagnostics that are output from your new testing module matches what you expecte

    •   I believe that in times like these, one is supposed to say: You are wicked
        and wrong to have broken inside and peeked at the implementation and then
        relied upon it.
       
      Let me say that the so-called 'screen-scraping' idea for T::B::T was entirely the author of Test::Builder's idea [perl.org] and uses only documented interfaces.

      The method of grabbing the screen output is documented, but exactly what gets output is not. The way I put it was:

      You are wicked and wrong to have scraped the

      • How could so many people miss such a widespread failure? What can be done to fix that?
        Let's face facts, we're busy, busy people. Rafael's point about monitoring releases (particularly beta ones) is a good one. I should have been doing that. But it's very hard - I don't have time to read the perl-qa list every week, and it's sometimes months between when I blast though each of my mailing lists. Why don't we look at what steps can be taken to make it easier to monitor what releases are coming out?

        I like the point about an automated tool, but I'm certainly not going to write one. Or I might, but if I do then I should find some way to allow other people to use it. And I don't mean just by giving them the tool to run too. I mean making some kind of service available.

        It's about time we produced some fine-grained notification method for new module releases. If this was a couple of years ago, I'd have said we could let people register email addresses. This day and age I'd say we need to have a system that people can subscribe to releases via their RSS readers.