On 07/08/2014 10:24, Alex Peshkoff wrote: > I can agree with your arguments provided you demonstrate a real world > sample where we need to inherit the implementation of interface. The > problem is that surprisingly named methods will be present always, but > need in implementation inheritance is rather suspicious - currently we > easily live without it. > > I do not look if we currently have any use of this, but the fact that we're talking about implementations, make clear for me that we should have something good for general use, as not only us Firebird project will have implementations, but plugins, etc.
In your scheme, other than the runtime malfunction of a class calling static method sometimes (via C++) and virtual from outside (via the interface), there is another issue. If one miss a method, it will also cause a runtime malfunction without a compile error. The dispatcher will keep calling itself recursively until crashes. So, it's *very* error prone. Adriano ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
