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

use Perl Log In

Log In

[ Create a new account ]

elliot (8136)

  (email not shown publicly)
AOL IM: elliotshank (Add Buddy, Send Message)
+ -

  Comment: I regularly take advantage of the runtime has(). (Score 1) on 2010.08.03 10:37

by elliot on 2010.08.03 10:37 (#72236)
Attached to: Protesting the Moose with sugary alternatives
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.

Read More 17 comments
Comments: 17
+ -

  Comment: My most common ones are pretty simple. (Score 1) on 2009.12.17 11:04

by elliot on 2009.12.17 11:04 (#71414)
Attached to: What's your coolest Perl one-liner?
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.

Read More 7 comments
Comments: 7
+ -

  Comment: "Don't worry, be happy" (Score 1) on 2009.11.17 12:03

by elliot on 2009.11.17 12:03 (#71154)
Attached to: Why no plan for nested TAP?

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().

Read More 14 comments
Comments: 14
+ -

  Comment: Re:My problem with Test::Most, et al.. (Score 1) on 2009.11.11 15:47

by elliot on 2009.11.11 15:47 (#71095)
Attached to: Test::Kit Production Release

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.

Read More 4 comments
Comments: 4
+ -

  Comment: My problem with Test::Most, et al.. (Score 1) on 2009.11.11 11:00

by elliot on 2009.11.11 11:00 (#71090)
Attached to: Test::Kit Production Release

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

Read More 4 comments
Comments: 4
+ -

  Comment: dpan (Score 1) on 2009.11.03 19:15

by elliot on 2009.11.03 19:15 (#71035)
Attached to: Using CPAN's Toolchain to Improve Your Code

Check out, 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.

Read More 5 comments
Comments: 5
+ -

  Comment: Don't use angle brackets?!? (Score 1) on 2009.10.26 21:13

by elliot on 2009.10.26 21:13 (#70982)
Attached to: Syntax Highlighting in Pod::Parser::Groffmom

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

Read More 4 comments
Comments: 4
+ -

  Comment: Dude, I can't believe you left this one out! (Score 1) on 2009.10.22 13:36

by elliot on 2009.10.22 13:36 (#70941)
Attached to: I'm a Perl::Critic committer.

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

Read More 6 comments
Comments: 6
+ -

  Comment: Re:Re-testing? (Score 1) on 2009.10.20 11:38

by elliot on 2009.10.20 11:38 (#70928)
Attached to: Downgrading Moose

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.

Read More 9 comments
Comments: 9
+ -

  Comment: Re:Hidden agenda? o.O (Score 1) on 2009.07.07 20:15

by elliot on 2009.07.07 20:15 (#69364)
Attached to: There is a word for that.....

Well, if he's right, then all of the people who have experience in maintaining perl 5 are wrong. Which seems very, very, unlikely, no?

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

Read More 19 comments
Comments: 19
+ -

  Comment: Enhancements (Score 1) on 2009.05.27 22:26

by elliot on 2009.05.27 22:26 (#68808)
Attached to: The Moose Class Hierarchy

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.

Read More 3 comments
Comments: 3
+ -

  Journal: The most significant Perl::Critic release in a long while. on 2009.01.01 16:01

Journal by elliot on 2009.01.01 16:01
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.
Read More 2 comments
Comments: 2
+ -

  Comment: Re:More smokers, please. (Score 1) on 2008.12.06 22:34

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

Read More 27 comments
Comments: 27
+ -

  Comment: More smokers, please. (Score 1) on 2008.12.06 14:28

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.

Read More 27 comments
Comments: 27