Frank Schönheit - Sun Microsystems Germany wrote:
Hi Stephan,
[...]
The idea was to move service instantiation into the language bindings
(so, e.g., in C++ a class implementing a service would probably have C++
class constructors matching the UNO service constructors, or static
factory methods, etc.).
That's something I didn't dare to suggest :).
Moving the ctor handling to the factories, instead of the current
"always default-construct and then late-initialize" would be even
better. For instance, implementations can get rid of all their "not
initialized" handling, in case somebody creates them bypassing the
explicit ctors, and does *not* subsequently initialize them.
The current XImplementation stuff is seen as a
gross hack to implement service constructors (at least by me).
+1
Unfortunately, this somehow keeps slipping on the urgent todo list...
Sad enough. Whenever I implement constructors, I find it pretty ugly to
do all this manual initialization coding.
See <http://www.openoffice.org/issues/show_bug.cgi?id=75053>, also at
<http://wiki.services.openoffice.org/wiki/Uno/To-Dos#Features>.
Hope that helps :)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
