use Perl

WTF is surreal precedence?

Oh, please post that in the comments on Flickr!

--Theory

How about "Strawberry Perl Workstation Edition" and "Strawberry Perl Server Edition"? It seems to me that most folks would only want the "lite" edition for running code on a server where they have no UI.

--Theory

It seems to me that it would be useful for Perl(5|6) to make method overriding explicit as Java has done. Similarly, I'd like to see it made explicit when you're overriding a role method with a method defined in a class. As a compile-time error.

So I think it'd be useful for you, Ovid, to implement a MooseX module that does this a al Stevan's suggestion. Then there'd be a feature that you could point people to using.

Stevan, FWIW, in Smalltalk the browser isn't just a tool, it's effectively part of the language. And although most Java programmers use tools (Eclipse), the @Override syntax has still been added to the language itself. So when the tools are not part of the language (as Perl::Critic is not required to write Perl and Eclipse is not required to write Java), I think that a feature of the language should be provided for you to be explicit about when you're overriding a method.

If Ovid can demonstrate this as useful in a MooseX module, so much the better.

My $0.02.

--Theory

This is great news, Adam, thanks! I'm looking forward to playing with it.

--Theory

What, can't anyone change just a single line? Everyone has to touch 0 or more? So much for Perl one-liners! ;-P

--Theory

Ah, I see. Except that it's not a key in a hash in that code, but a method.

--Theory

% perldoc -f expand
No documentation for perl function `expand' found

--Theory

Personally, I hate the style where you test something at the beginning of a statement and then do something if it's true by using and. I much prefer using if or unless at the end of a statement:

    my $_combination_info = {};
    sub combination_info {
        my $self = shift;
        $_combination_info->{ $self->csv_file_name } = shift if @_;
        return $_combination_info->{ $self->csv_file_name };
    }

I use this style all the time. But I have to say, I don't think that your original example was clever, but indicative of someone who prefers a different style of handling one-line conditionals. I would even argue that it's not really idiomatic Perl, but it's not in any way clever.

--Theory

I can see where you're going with this, Ovid. Can Test::Smell be far behind (um, pun not intended)?

I can see it testing all of the classes in your project and emitting passes or failures for inheritance patterns, hidden method, long method bodies, etc.