Hello Marten, Dan, * > Go away from language bindings at the first > level API and make a totally language independent > API with a defined call structure for C.
I don't see the problem, maybe I don't get your point. The main UNO base libraries like libcppu and libsal and every bridge library actually export pure C symbols. Connecting a specific language to UNO is actually connecting that language to a C-style interface, i.e. struct uno_Interface (in uno/dispatcher.h) which defines a generic dispatcher. All surrounded types, meta types etc. are all defined in C. As a background: Objects from different languages are divided into what we call "environments". There is one central environment that every language binding/bridge connects to, which is the above mentioned "binary C UNO environment". This way we can cross connect any languages : C++ --------\ /-------- C++ Java -------- binary C UNO -------- Java Pyton ------/ \----- Python CLI etal --/ \-- CLI etal ... regards, --Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
