Hi all, I am less experience on the udk. :-) Who can give me some suggestion how to start the task(Clear Separation between C and Cpp and Core Components)? the task's link as follow: http://wiki.services.openoffice.org/wiki/Uno/Todo/Clear_Separation_between_C_and_Cpp_and_Core_Components
Such as the first step: Move C++ stuff from udk/cppu to udk/cppuhelper. Which files need to be moved ? Regards, Liyuan > Hi Stephan, > > Stephan Bergmann wrote: >> >> Thanks for taking interest. Anyway, not directly related to your >> request, I have some troubles with that todo. Quoting from that wiki page: >> >> "There are various obstacles in the way to cleanly separate C Uno (AKA >> Binary Uno) from C++ Uno. Some of these are >> >> * the C Uno runtime is implemented in C++," >> >> In how far is that a problem? > In case that we understand a clean separation of the C and C++ Uno > runtimes in a way, that the C++ runtime is implemented on top of the C > runtime, than the C runtime may not be implemented by using elements > (headers) of the C++. > > You could argue, that the C runtime may very well use C++ inline stuff > from the C++ runtime, which is valid, but please see below. >> >> "* a C++ Uno runtime would be stacked on top of C Uno, >> * there is no living C language binding," >> >> Do we want one? > Yes, I think so. A C runtime likely makes Uno more attractive to other > projects. >> >> "* the C++ Uno runtime offers various functions for bootstrapping Uno, >> which are not yet available for Binary Uno." >> >> Again, do we need them? > See above. >> >> "* Upper level modules headers may not be used, until they are >> delivered, even if they are self contained." >> >> What is meant with that? > What I want to say is, that in a lower module you may not use upper > level implementations, even in case they are completely inline, as > during building the upper levels are not yet delivered. >> >> -Stephan > > Kay > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
