On 4 June 2013 21:43, Dicebot <m.strashun@gmail.com> wrote:

- Can not be un-done by the compiler/linker like it can in other
(dynamic) languages. No sufficiently smart compiler can ever address this
problem as an optimisation.

It can be done if you are fine marking every single class supposed to be used across the binary boundaries as "export". See deadalnix explanations in this thread for details.

I don't see how it's an intuitive connection between 'export' and 'virtual-by-default'. And it doesn't address the accessor/property problem, which would often remain inlined even across a DLL.

It also relies on non-standard/unexpected behaviour for .so's (which export everything right?).