No run-time substitution of a vtable's method pointers : why?? How is that in anyway more efficient, needed. You still need to write boilerplate code to make the decision to actually change the vtable method pointers change to something else. You could always move that decision to compile time (use templates)
Slashdot Mirror
No run-time substitution of a vtable's method pointers : why?? How is that in anyway more efficient, needed. You still need to write boilerplate code to make the decision to actually change the vtable method pointers change to something else. You could always move that decision to compile time (use templates)