Thank you both! That's very helpful...
...and thanks for the kick in the brain Stevan: your suggestion of using
composition here makes a lot more sense than the solutions I was coming up
with... I think I got lost (refactoring a large ten-year-old legacy app's
multiple parallel data-structures) an
Hi Montgomery,
I don't have a ready answer to your problem, but I'm going to discuss what I
feel is a more general issue, which I've been thinking about it the past few
days.
On Tuesday 20 Apr 2010 04:01:09 Montgomery Conner wrote:
> Hi All,
>
> I've got a question that I didn't see addressed
On Apr 19, 2010, at 9:01 PM, Montgomery Conner wrote:
Can anyone offer some insight into how something like this
might be implemented?
Honestly, I would use an embedded object instead of a compound data
structure.
If chaining M::M::A::N handlers isn't natively possible, does anyone
have
Hi All,
I've got a question that I didn't see addressed in any of the fine Moose
documentation... or maybe I just missed it. At any rate, it seems like a
common enough case that I thought others may benefit from my problem...
Say I have an attribute that represents a one-to-many relationship
impl
