RSS | Module Info | Add a review of MooseX-MethodAttributes

2 out of 5 found this review helpful:

MooseX-MethodAttributes (0.16) *****

To help people figure out the "why?" here, my understanding is that even though in general the Perl community is moving away from method attributes, there's a lot of code in the wild that uses it, so the Moose community went to a lot of trouble (mostly the main author of this package) to bend over backwards and support something that few people using Moose actually need, but was felt needed for compatibility reasons. I think the main reason for being for this (please someone correct me if I am wrong) is to support the Catalyst transition to Moose. So I feel it really shows how hard the Catalyst team is trying to maintain backward compatibility, even with as huge a change as rewriting the underlying bits in a new framework.

My recommendation to you is to stay away from method attributes; but if you have legacy code that uses then and you want to transition to Moose, this will help a lot.

john napiorkowski - 2009-09-15 02:01:00
Was this review helpful to you?  Yes No

5 out of 8 found this review helpful:

MooseX-MethodAttributes (0.14)

There are those who believe that all language features should be introspectable by an consistent object-oriented interface, and then those who believe that piecemeal procedural interfaces are sufficient.

If you're not sold on the first idea, you might reach the conclusion of Pista. In which case continue to use the old interfaces of yesterday, and hope that people don't ever call your code legacy as soon as you write it.

Sam Vilain - 2009-06-14 15:35:05
Was this review helpful to you?  Yes No

9 out of 10 found this review helpful:

MooseX-MethodAttributes (0.12)

This is a perfectly reasonable interface to code attributes inside the Moose metaprotocol. However, since I haven't actually used it (just code that uses it), I won't give it a numeric rating.

Dear Pista Palo: while you're at it, also rate POE 1 star for being more code than "while (1) {}", rate Template::Toolkit 1 star for being more code than sprintf, and rate DBI 1 star for being more code than `mysql -e "select * from mytable" mydb`.

hdp - 2009-05-25 21:19:18
Was this review helpful to you?  Yes No

2 out of 23 found this review helpful:

MooseX-MethodAttributes (0.18) *

For today's edition of "CPAN one-liners," we have ten -- count 'em, ten! -- classes and a random dependency on namespace::clean to replace this:

use attributes; attributes::get(\&f)

with this:

use MooseX::MethodAttributes; @{main->meta->get_method('f')->attributes}

hdp: There is being dishonestly clueless, and then there is that thing you're doing. Please stop.

Sam, Sam, Sam... There are those who believe that simple procedural interfaces are sufficient for many language features, and those that believe that all must be accessed by pedantically "object-oriented" interfaces.

If you're not sold on the first idea, you might reach the conclusion of Sam. In which case, please continue to reinvent wheels badly, and hope that people don't ever cally your code "pointless style fapping" as soon as you write it.

Pista Palo - 2009-05-25 07:35:14
Was this review helpful to you?  Yes No


the camel