4 Jul
2010
4 Jul
'10
5:02 a.m.
2010/7/2 Jon Cruz <jon@...18...>:
Yes.
The vtable is the main issue here.
If a class has no virtual functions and no vtable, then it's memory layout is equivalent to a C struct. However...
... once you add a virtual function into the mix, object instances generally get a hidden pointer to the appropriate vtable. That hidden pointer bumps things around and confuses C code that is expecting a precise memory layout.
So what exactly is this "C++ification" intended to do? Syntax support for virtual functions is one of the main advantages of moving to C++.
I also thought the goal is to move off GObject for the SP tree, so rewriting functionality dependent on GObject should be part of the project.
Regards, Krzysztof