Re^2: How Should I Relate Many Objects Of One Kind To A Single, Common Object Of Another

in reply to Re: How Should I Relate Many Objects Of One Kind To A Single, Common Object Of Another
in thread How Should I Relate Many Objects Of One Kind To A Single, Common Object Of Another

Amazing. You rapped this out in three hours?! Thanks.

By trying to use a rider as the object that ties the pieces together, I created an illogical structure held up with a misuse of inheritance. (I'd still like to use a rider as the primary object, but this approach is undoubtedly more logical and therefore more comprehensible.)

Thanks again!

Comment on Re^2: How Should I Relate Many Objects Of One Kind To A Single, Common Object Of Another

Replies are listed 'Best First'.
Re^3: How Should I Relate Many Objects Of One Kind To A Single, Common Object Of Another by tobyink (Canon) on May 25, 2012 at 21:46 UTC
Inheritance is just one relationship that objects and classes can be put into. Delegation, aggregation, composition, etc are sometimes overlooked `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply]

In Section Seekers of Perl Wisdom