a bad idea. Why was override a bad idea?.
I thing it was a good idea. Especially in an api which requires a service a default working implementation could be defined (without requiring the user to do anything). A user however could overwrite it (maybe using the default implementation with differnt properties). I think this is what overridable was thought for.
When overridable is not present I don't know a realy convient way with which you could achieve this. Ie if you use extension-points, it is much less convinient for the programmer (I guess you would always use more classes / interfaces) and generally less flexible for the user.
Maybe you could tell me a way how to achive the same effect without overridable.
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
