3 ms·
To be honest, a derived class already cannot be a POD. But stuffing the vtable pointer into any derived class is indeed wasteful for embedded programming and op
by pandaman 10y ago
To be honest, a derived class already cannot be a POD. But stuffing the vtable pointer into any derived class is indeed wasteful for embedded programming and opens another way to exploit your system (if you care about security) by leaving code pointers at the fixed addresses in r/w memory.
- gpderetta 10y agoit can still be standard layout (the 'new' POD for all intents and purposes) if either the base or the derived class is empty. /pedantic