Re: Meta::Attribute::Native::Trait vs MooseX::AttributeHelpers

[Jurgen Pletinckx]

2009/10/26 Evan Carroll li...@evancarroll.com:
 I just noticed core Moose has traits now for Arrays (and other base
 types). How does this compare with the more traditional
 MX::AttributeHelpers metaclasses? There seems to be an undocumented
 overlap of functionality and I'm confused which one I should use. Any
 advice appreciated.

M::M::A::N is the new and improved MX::AH. It has been brought into
the core from the wasteland of the MX namespace. Ahem.

See also 
http://search.cpan.org/~drolsky/Moose-0.92/lib/Moose/Manual/Delta.pod#Version_0.89_01

It seems that a statement to that effect in the documentation for
the actual modules would be useful. Where did I leave my stack
of tuits?

-- 
Jurgen Pletinckx

Re: Meta::Attribute::Native::Trait vs MooseX::AttributeHelpers

[Evan Carroll]

It is hard to have these discussions being banned from IRC, but maybe
- beyond a notice in MX:AH deprecation - some functionality notifying
the user of an API change is required? Like something in MX:AH that
when used with a Moose  .90 the attribute traits would output a nice
warning message.

Warning the functionality of MooseX::AttributeHelpers has been moved
to core, please reference Moose::Meta::Attribute::Native for the new
API.

I've often thought that warnings were better explicit and overly
verbose in libraries and disabled via -X by the end user, but maybe an
env DEVELOPMENT flag would be just as useful. There are at least a few
examples of where as a developer I was stung with stuff that was
currently supported but deprecated, supported but retarded, or
implemented but unsupported.

-- 
Evan Carroll
System Lord of the Internets
http://www.evancarroll.com