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.
  • There's this zero-tolerance attitude many coders exhibit which only allows perfect code which might work in the lab, but as soon as you throw it into production environments problems surface. And often nobody's willing to change the implementation because it would involve a workaround which might break the perfect design. Telling somebody that the database you've been using for the last 10 years is the culprit and you should switch to another one (just to make this one module work correctly) is just plain
    • Funny you should mention PHP because I was thinking about a blog post defending PHP programmers. At the end of the day, those people who rip on PHP (and its programmers), are often bad about asking why it's so successful. Many people rail against the issues with PHP, but I doubt that most, if any, of them have produced perfect code. Hell, we're Perl programmers. We might defend lack of method and subroutine signatures because "that method is deep in the system and can't get bad arguments", but that's a

  • I still have in my mind some sort of graphical test tool for Perl, but I don't know what I quite want it to do and what new features, techniques, and consequences would come out of it.

    Test::Aggregate certainly comes out of the consequences of mainstream Perl testing and the framework that most everyone uses. It's what works right now: "Do what you can, with what you have, where you are".

    Without any goal or intention of actually implementing something new, if you started all over with whatever test harness y

    • Off the top of my head, there are a few things I would want. First, I'd want tests installed with modules. That would allow us to test our current installation, not just the module we intend to install.

      Second, I'd want a way to track tests over time. That would be difficult and I'm not sure how we would do it, but basically, if test some-cpan-module/t/foo.t fails in a particular way that we can live with and it fails in the same way after we upgrade other modules, we can at least have a controlled enviro