Am 19/11/2018 um 08:37 schrieb waddlesplash:
> With the API we have, we don't have much choices.
> If you have a better solution for future APIs, feel free to discuss
> them :-)
I'm confused. Aren't the APIs in question in the new libcodec, which is well on its way to being public API indeed, but until now was private API and not used anywhere but internally? So then ABI considerations are irrelevant here.
On an unrelated note: is there any work being done, say in newer C++ standards, to solve the FBC problem? It seems to me the virtual functions issue at least could be solved by generating the vtables at dynamic link time... but I don't know if anyone's been crazy enough to suggest an ABI like that.
