Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • What happens if you add CPAN tests to that count? And whatever is the Ruby equivalent.

    • Tough to say. According to Tim's slides, if we include bundled libraries, we drop significantly to a 7 to 1 advantage for tests. However, there's no clear way I can see to design a reasonable metric for non-core tests. LOC/test is silly, particularly since core Ruby seems to generate terser code than core Perl for similar functionality. Tests per function point would be difficult to analyze without static analysis of function points and agreement on said analysis.

      To be fair, even the core tests might be

      • Was thinking also about things like CPAN Testers. 3,592,446 public test reports (as of last night) vs ???.

        At least as evidence of a "testing culture". :-)

        -- dagolden

        • Heh :)

          I'm unaware of any other language community having anything remotely comparable.

          • ... yet.

            Many of the repositories are within a few years of us, so it's important to not get too proud about what we have, and keep pushing ahead.

            • First, those language communities have to get serious about including systematic automated testing throughout their repositories. I hope they do, but I haven't seen it.

              • That doesn’t really affect Adam’s point. Most of the infrastructure we have was built by individual efforts, so other communities with enough sufficiently determined members could clearly duplicate it in a reasonable time frame. (My gut estimate is about 3 years all told.)

                Even if other communities show no signs of such an effort and seem to be parsecs behind, that doesn’t mean we shouldn’t still keep pushing forward as if the would-be competition were breathing down our necks.

                Even if

                • Even if that image falsely assumes that this is a competition in the first place.

                  I don't believe it is. I want to see a comprehensive and freely distributable and reusable test suite for every widely used language. That's the only way we can port them to Parrot, for example. (There's also the code quality issue. Can I assume everyone understands that by now?)

                  • by jpedrosa (9172) on 2009.04.17 16:55 (#68164)
                    Thanks for the Perl 6 numbers. Speaking of more languages to Parrot, how is JavaScript coming along? Or ECMAScript? Because Google's v8 engine is a pretty good indication that JavaScript is a potential competitor for the server side needs as well. I have been creating some benchmarks and it fairs quite well against Ruby 1.9, Python and PHP, and while I don't like reinventing the wheel or the code bloat of JavaScript when compared to Ruby, it's certainly a platform to more than watch. See k7: []