Re: BUG #1589: The whole concept of forces/move_with_forces/forces_holder needs to be rethought

[Gervase Lam]

> From: David Philippi <address@hidden>
> Subject: Re: BUG #1589: The whole concept of
> forces/move_with_forces/forces_holder needs to be rethought Date: Wed, 6
> Nov 2002 13:51:13 +0100

> Because you would either have to include the same collision code in
> diffe= rent=20
> actions or you would have to derive the actions from=20
> PinguActionCollidingByMethodX
> where X is the right base class for the current action. The first
> would=20 introduce redundant code and the second creates an ugly class
> hierarchie.

My idea was more like the latter idea except that instead of putting the 
"collision code" into PinguActionCollidingByMethodX, it would be put into 
PinguAction as a virtual function with possibly a default function 
definition.

Each action, which is derived from PinguAction, can then override the 
virtual function.

Isn't this tidier and therefore better than using member templates?  Or am 
I missing something?

Thanks,
Gervase.