I think it would be best to "prototype" a new feature to accomplish
this in MooseX::* and we can push it back to core when it is vetted.
I think formalizing the setting-of-value process in the MOP may be
required to do this, so we will need to discuss this and putting it
into core.
- Stevan
On Jul 22, 2008, at 7:18 AM, Paul Driver wrote:
I think the major benefit of the "around" trigger was being able to
filter
the value going into the setter. I don't have any use case for
'before'
that couldn't be accomplished with older "standard" (after)
triggers - so
some kind of setter-filter (needs a better name) would probably do
just as
well. That could be done by a MooseX, potentially.
On Mon, Jul 21, 2008 at 8:10 PM, Stevan Little <
[EMAIL PROTECTED]> wrote:
Sartak, frodwith,
So I was looking over the trigger before/after/around patches and
something
occurred to me, trigger always expects a fully formed instance (I
know all
my uses do) and with the before/after/around trigger that is just not
possible, especially for trigger at construction time.
So unfortunately this means we need to remove this patch and
rethink this
feature.
- Stevan
