S
Stefan Ram
I read someone "invented" vtables. But to me it seems that
they are obvious in the sense that a class is a list of
methods (simplified), which gives the vtable, and an object
has a class, which means that the object holds a pointer to
a vtable.
I cannot think of another means to implement virtual member
functions.
Is there something non-obvious about vtables that has to be
"invented"?
Are there other reasonable possibilities to implement
virtual calls?
they are obvious in the sense that a class is a list of
methods (simplified), which gives the vtable, and an object
has a class, which means that the object holds a pointer to
a vtable.
I cannot think of another means to implement virtual member
functions.
Is there something non-obvious about vtables that has to be
"invented"?
Are there other reasonable possibilities to implement
virtual calls?