Timeline for Avoiding vtable pointers in objects in C++
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2018 at 15:19 | history | protected | gnat | ||
| Nov 20, 2018 at 14:25 | answer | added | Brian | timeline score: 3 | |
| Oct 11, 2018 at 22:40 | comment | added | rwong | I wonder if this is related to the necessity of thunking - adjusting pointer address as part of down-casting to an interface (abstract base class) pointer, as well as before/after function calls? The need to have unique address makes it necessary to have at least that same number of vtable pointers. | |
| Oct 11, 2018 at 10:05 | comment | added | Deduplicator | If you have a good-enough reason, implementing some traits-type isn't too difficult. The lack of language-level-support makes it a lot more verbose though, no way around it. At least implicit traitt instantiations can easily be supported with templates. | |
| Oct 11, 2018 at 9:20 | answer | added | groovyspaceman | timeline score: 0 | |
| Aug 6, 2018 at 13:36 | comment | added | Basile Starynkevitch | In practice it does not matter: multiple inheritance is rarely used, and in the few cases it is used the object is usually quite "big" -data fields are also inherited- (and the multiple superclasses are few, more often 2 than 5). | |
| Aug 6, 2018 at 6:02 | review | Close votes | |||
| Aug 11, 2018 at 3:05 | |||||
| Aug 6, 2018 at 4:53 | answer | added | Erik Eidt | timeline score: 4 | |
| Aug 6, 2018 at 4:30 | answer | added | Nicol Bolas | timeline score: 10 | |
| Aug 6, 2018 at 4:08 | history | asked | Clinton | CC BY-SA 4.0 |