Aaron Held wrote:
We should have both.
I like subclassing when I change the basic implementation (data level),
and hooks/callbacks/plugins where I need to
add code that responds to events of the basic web application flow.
Agreed.
In my option, the desire of users to subclass basic classes like
Ian Bicking wrote:
Jason Hildebrand wrote:
I eventually realized that using classes would clean a lot of this up.
With classes you only need one method per event. Any subclass which
overrides this method can call the superclass' method (or not) when it
needs to, thereby controlling whether the ne
