Re: TPF Devel::Cover grant report Week 18

On Oct 1, 2012, at 2:00 AM, Ovid wrote: > For others: yes, I know that PPI offers cyclomatic complexity information. I > would like to see all code coverage information provided in "one-stop > shopping" for Perl rather than relying on a separate tool (and I don't know > that PPI exposes the co

[Module Announcement] Pinto

Pinto is a sophisticated application for managing Perl module dependencies. You may have heard about it from my presentation at YAPC earlier this year. In the last few months, Pinto has continued to evolve. The latest release includes a version control mechanism that allows you to review chan

version.pm and developer version numbers

I just discovered that version.pm always treats version numbers with an underscore as less than the equivalent version number without the underscore. So "6.63_02" is less than "6.6302". Is it it just me, or does that seem crazy? Dealing with $VERSION numbers in Perl is hard enough as it is. T

What is the "best" code on the CPAN?

I'm working with a group of Perl developers with various backgrounds and skill levels. We have instituted a fairly effective code inspection process, but we still get bogged down in debates over what "good code" is. Unfortunately, the developers work in isolated silos and spend the vast major

Re: Need suggestions for terminology

On Dec 2, 2011, at 7:48 PM, David Golden wrote: > I would encourage you to use existing names/conventions whenever > possible. Some references to consider if you haven't. Thanks for reminding me about your blog post on the subject -- I had forgotten about that. And I read some other interesti

Re: Need suggestions for terminology

On Dec 2, 2011, at 7:10 PM, Michael G Schwern wrote: >> Distribution: A Distribution is an abstract concept that defines >> relationships between packages. The minimal concrete implementation >> of a Distribution would be just a META.json (or equivalent) file. >> Distributions also have names a

Need suggestions for terminology

Hi everyone- I need some suggestions for terminology to use in my code and documentation. I'm picky about names, so this is important to me (perhaps more than it should be). The context is Pinto, which is yet-another suite of libraries and tools for building a private CPAN-like repository. H

Re: RFC: Private CPAN In A Box

s polluting the pure environment that you're trying to build in. Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: RFC: Private CPAN In A Box

difference is how that distro get's delivered into the lpan. Off to bed now. Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: RFC: Private CPAN In A Box

ion will have its own lpan. Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: RFC: Private CPAN In A Box

he associated projects. So the project remains physically self-contained, but logically shares the same lpan with related projects. But I don't know how you would do this with git. Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: RFC: Private CPAN In A Box

quire rejiggering the entire CPAN tool chain and/or backfilling CPAN distros with some new metadata. I realize this doesn't solve the "big" problem of automatically building a particular CPAN mirror with a magical mix modules. But based on my own development patterns, I think this model could provide a workable framework for organically evolving application dependencies, while providing a stable and reproducible dependency stack at the same time. What do you think? Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: RFC: Private CPAN In A Box

e http://cp2011-05an.barnyard.co.uk/). The concept of a CPAN server also provides a convenient hook for plugging in other services, like a private PAUSE or MetaCPAN. I'm not saying that *the* CPAN should work this way. I'm just suggesting that a *private* CPAN could work this way. Jeffr

Re: RFC: Private CPAN In A Box

ot of organizations. Somehow, I want to try and package that idea in a way that might appeal to a wide audience. Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: RFC: Private CPAN In A Box

ply permitted authors to express precisely which $VERSION of something they require. So I have to wonder if that is the right place to focus, rather than building something on top of the tool chain. Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

RFC: Private CPAN In A Box

NOTE: This was also posted on perlmonks at http://perlmonks.org/?node_id=905878. I'm trying to reach a wide audience, so I'm posting it here too. Over the last few years, I've helped build private CPANs (DarkPANs or DPANs as brian d foy calls them) for 3 different organizations. Each time I co

Re: standard for internal-only tests?

On Jul 31, 2009, at 11:32 AM, Jonathan Swartz wrote: Anyone who is running 'make test' in the git source will see the internal tests, as they should...anyone who has the published distribution won't see them. IMHO, you should still include author-only tests in your published distributio

Should MANIFEST go in the repository?

c. So what are the best practices for managing distro metafiles (MANIFEST in particular)? Jeffrey Thalhammer Imaginative Software Systems vcard: http://www.imaginative-software.com/contact/jeff.vcf

Re: Pod::Critic?

> I've written plenty of modules with lots of code > but very minimal external interfaces that need only > a page to describe. In such cases, do you find that you've used more comments in the code? This it isn't quite the same metric, but there is probably some ratio of code to non-code that most

Re: Pod::Critic?

--- Ian Malpass <[EMAIL PROTECTED]> wrote: > I've been documenting lately, so I'm a bit > POD-focussed at the moment :) I was pondering > creating Pod::Critic, as a documentation analogue > of Perl::Critic. Some other ideas (not suitable for everyone)... RequireCompilableSynopsis - For modules

Module Announcement: Perl-Critic-1.01

After more than 18 months of development, Perl-Critic has reached its first major release! Version 1.01 is now available on a CPAN mirror near you. For those of you who aren't familiar with it, Perl-Critic is a highly flexible static source code analyzer

Re: Proposed kwalitee metric: consistent_newlines

> So I'd like to propose the following for inclusion. > > Metric: consistent_newlines > > The distribution is awarded a point IF for ALL text > files within the distribution EACH file contains > EITHER exclusively unix newlines OR exclusively > Win32 newlines. In addition, I'd be happy to cook

[OT] TDD + Pair Programming

I have never actually had an opportunity to practice this, but I've always felt that the most obvious way to combine test-driven development with pair programming was to have one person write test code while the other person writes application code. Presumably they might change roles periodically,

Re: Best Practice for testing compilation of scripts

I just found http://search.cpan.org/dist/Test-Strict, which was written by one of my co-workers. Among other cool things, it has a C function which does the same thing. It still uses backticks and redirection which may not be too portable, but it will suit my needs. Still, a C function seems lik

Best Practice for testing compilation of scripts

Putting aside the argument that most logic should be in libraries and not scripts, what is the best practice for writing test cases to verify that your Perl scripts compile? My quick and dirty solution is something like: use Test::More tests => 1; chomp (my $output = `perl -c $script 2>&1`); i

Re: Trends in Code Quality

> If you want to equip programmers to talk to > management, don’t > forget to give them this link: > http://www.martinfowler.com/bliki/TechnicalDebt.html Thanks for this. I've heard the term "Technical Debt" a few times lately and I really like it. Unlike a financial debt however, there is a p

Re: Trends in Code Quality

> If you're talking to a bunch of perl mongers I > recommend talking about > perl instead of spouting management-speak. The > Republic Of Ireland has > nothing to do with perl programming. I can appreciate that, but I have to believe that no one likes writing crappy code. And more so, no one l

Re: Trends in Code Quality

> >By lowering maintenance costs via quality control, > managers can > >avoid (or at least postpone) having to scrap their > entire system > >and rebuild from scratch in India. > > I think this is a bit of a stretch. I'm in the middle of one such situation. I have inherited a 500k line legacy sy

Trends in Code Quality

Hello everyone- I'm working on a presentation of Perl::Critic for the local perlmongers group. As part of the presentation, I would like to make some comments about the current industry trends around software quality. Basically, I'd like to assert that there is a growing emphasis on software qua

Re: Dependency trees was: CPAN Upload: D/DO/DOMM/Module-CPANTS-Analyse-0.5.tar.gz

Randy Kobes distributes Win32 PPMs for some of the modules that ActiveState doesn't provide. It is not entirely automated, so the latest code isn't always available. But Randy is very helpful if there's anything you want to see. http://theoryx5.uwinnipeg.ca/ppms/ -Jeff > > I'm somewhat new to

Test Script Best-Practices

Greetings, I've noticed that CPAN authors use a variety of techniques to manipulate the run-time environment in their test scripts. Usually, it involves changing directories and/or altering @INC. This one seem pretty popular: BEGIN { if($ENV{PERL_CORE}) { #What is "PERL_CORE"?