use Perl

I've got a bunch of places where I generate attributes at module run time. This is useful when attributes have things in common.

Theoretically, Moose could use Hooks::EndOfScope like namespace::clean, but having a dividing line in the middle of a module can be useful.

If someone would get his act together, we'd have a non-dev release of Perl::Critic::Moose out that can check a lot of this stuff for you, e.g. that you don't use with() multiple times.

perl -MSome::Module -e 0

perl -E 'say foreach split ":", $ENV{PATH}' # Or other pathlike thing.

ack --text -l '\bv1.2.3\b' | xargs perl -pi -e 's/\bv1\.2\.3\b/v1.2.4/g'

Otherwise, it's mostly experiments; I prefer bash to a REPL.

Regardless of what you think about counting tests, I think this is a significant change of the way that Test::More works. Up until now, everything has had to be explicit, whether through "tests", "no_plan", or done_testing().

I didn't say I was rational about it. :]

But even if T::M puts unused stuff, that's no excuse for piling in more.

Is importing a bunch of functions one may never use. The unnecessary namespace pollution makes me cringe.

Check out http://search.cpan.org/dist/MyCPAN-App-DPAN/, which allows you to start from nothing, rather than having to have some existing setup. This allows you to curate what modules are in your local repository, in particular meaning that you can easily dictate which version of a distribution you have.

I'm in trouble then. Angle brackets is about all I use nowadays. :]

Given your comments on my code, you wanted Modules::RequireUseOfTheEntireCPANIncludingBioPerlAndAngerwhale.

My question is why are your dependencies in a different checkout? We've got a directory with all versions of any CPAN dependencies we've ever used, but it's just a flat directory and simply acts as a central place for different projects to copy things from.

Each project has its own DarkPAN and we point CPAN(PLUS)? at that. When we want to change the version of something, we just "svn rm" the current version in the project's DPAN, "svn cp" the tarball from the central directory, and rebuild the indexes.

What's with the absolutism? Cannot they both be partially right and partially wrong?

The most significant, yet theoretically easy thing that I can think of would be identifying classes vs roles.

Yeah, I could go for the full thing and have arrows indicating role consumption, etc., but a simple identification of which things were concrete and which were not would be a help.

Perl::Critic 1.094 is on its way to a CPAN mirror near you. There are a number of changes in it, but there's one in particular that I want to point out. A new policy called Miscellanea::ProhibitUselessNoCritic.

But nowhere near the number that there are for other platforms. The number of Windows reports I get is way too small.

For testing purposes, I don't want to personally log into six different O/Ss. It would be nice if a CPAN smoker was set up for each Strawberry and Windows combination.