User1928065626 posted
Hi, I came across a post on Virtual Table which states "A virtual method table is a mechanism used in a programming language to support dynamic dispatch (or run-time methodbinding)."
Basically the idea is child classes of a super class either can use the default virtual method of the super class as is, or they can override the default virtual method of the super class and give their own implementation for the method as they see
fit.
The example of this concept given by the author of the post reminds me of the Strategy Pattern. It appears this method can bind data at run-time very much the same way that the Strategy Pattern does.
Am I correct in assuming that the Virtual Method Table can be used to do the same thing that the Strategy Pattern can do?
Please see the link below for more details on virtual method table.
https://en.wikipedia.org/wiki/Virtual_method_table