Migrating engine and library code bases to C++, the engine main routine became the mixture of C++ and C(GObject) code, containing iBus API calling code. Because of simplicity and portability, we are migrating code base to C++.
However, there was problem called "C++ ABI transition problem" when SCIM was activity developed.
Its approximate concept is the C binary and C++ binary aren't fully interoperable to each other. There's risk for calling sub-routines of C, C++ each other.
Still, we don't know what it really is, but we want to fully understand the risk for mixing C and C++ code. Study and sharing knowledge are suggested
Migrating engine and library code bases to C++, the engine main routine became the mixture of C++ and C(GObject) code, containing iBus API calling code. Because of simplicity and portability, we are migrating code base to C++. However, there was problem called "C++ ABI transition problem" when SCIM was activity developed. Its approximate concept is the C binary and C++ binary aren't fully interoperable to each other. There's risk for calling sub-routines of C, C++ each other. Still, we don't know what it really is, but we want to fully understand the risk for mixing C and C++ code. Study and sharing knowledge are suggested