Thanks for the additional insights Neophytos.
Maybe there is space for some discussion about this. I think one should expect generic logic to be inherited when using next, rather than be wiped out by specific method definition.
Here on OpenACS, I think the only class who redefined the save method is CrItem. The method is completely overwritten there, meaning that no use of the 'next' idiom is done. This is becuse CrItems need some really specific behavior to handle revisions and such.
Of course there could be people out there who wrote code with current behavior in mind and used 'next' in their 'save' implementation. If we just turn on inheritance, they will end up with code updating their objects twice... could not be a big deal in the transition phase, yet it's dangerous.
I think this deserves some thinking...
