Re: Keeping relationally child objects alive with Moo

What you describe is called "composition", and it's often accompanied by "delegation" where the outer object delegates some of its method to the inner one. It's a common pattern and it should work flawlessly in Moo.

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Comment on Re: Keeping relationally child objects alive with Moo Download Code

Replies are listed 'Best First'.
Re^2: Keeping relationally child objects alive with Moo by anonymized user 468275 (Curate) on Sep 21, 2017 at 14:07 UTC
That's reassuring, but what about the way I am doing it: `$self->attribute->{'key'} = $childObject;` [download] Is this the right way to assign one of many relationally child objects to the relational parent object? Having had some problems I worked around explicitly, I am worried that the reference to the inner object in the above construction is too remote to persist indefinitely just because the parent object persists indefinitely. One world, one people	[reply] [d/l]
Re^3: Keeping relationally child objects alive with Moo by Corion (Patriarch) on Sep 21, 2017 at 14:17 UTC
So, what does `->attribute` return? If it returns a hashref that is kept alive by `$self`, you should be fine. If it returns something else, you might have a problem. But we cannot tell without seeing some representative example.	[reply] [d/l] [select]
Re^4: Keeping relationally child objects alive with Moo by anonymized user 468275 (Curate) on Sep 21, 2017 at 15:58 UTC
The hash keys persist, but sometimes the values (objects) get destroyed/go undef even though obviously $self and all its immediate attributes are still alive and well. One world, one people	[reply]