Can you detail more what this change is and why?
Best I can tell from the other thread and the github commit views was
that it just adds a bunch of methods to Moose::Meta::Attribute that
delegate to the instance inliners. I am not sure what this buys you
beyond less code to write and hiding the instance protocol.
My concern is that the instance meta-object is actually associated
with the meta-class, not with the attribute meta-object so by pushing
this in here it will make things more confusing.
- Stevan
On Nov 9, 2009, at 5:14 PM, Nathan Gass wrote:
Hello
Sorry about the repeated double posting, I just don't want to wait
until my
mail with the wrong From: line comes through.
The code/branch I talk about lives at
http://github.com/xabbu42/class-mop/tree/topic/attribute-controls-storage
and
http://github.com/xabbu42/moose/tree/topic/attribute-controls-storage
As discussed in the thread MooseX::Attribute::Delegated I created a
topic
branch topic/attribute-controls-storage which makes it easier to
overwrite the
way a single attribute is stored in the object.
The smolder script gives me no new failures (MooseX::Daemonize and
MooseX::Types::Structured currently fail for me with 0.92 and my
branch)
and one new warning, which is related to other changes since 0.92
(deprecation
of get_attribute_map).
Any help/tips for extending on documentation and tests is very
appreciated.
Comments?
Greetings
xabbu42
