On Nov 15, 2008, at 3:31 PM, Michael Potter wrote:
Fine. I would love to know a straightforward work-around though,
that does
not drastically alter class structures. Would it be to much to ask
for an
option to 'has +' that simply disables any accessor generation (and
provides/curries methods), that is totally *use-at-own-risk* and would
assume all the appropriate methods were installed in the base class?
Something like:
has +foo => (
inherit_accessors => (1|0)
);
wouldn't be too objectionable, however before we put that into core I
would like to see if as a MooseX:: module so we can work out all the
possible issues first.
- Stevan
