One nit: since the automatic implementation name derivation looks kind
of fragile (and most of the time, I _do_ declare my service
implementations in anonymous namespaces) - how about disabling that
feature by default? I have the impression that not much of OOo
development outside Sun takes
Hi Daniel,
I'd like to present/discuss a recent helper I have developed which IMO
simplifies the implementation of UNO services in C++ a lot.
Using the following (what I call) service declaration, the developer can
concentrate on implementing her service's interfaces, e.g.
again, you managed
Hello Niklas,
namespace sdecl = comphelper::service_decl;
sdecl::ServiceDecl const myDecl(
sdecl::class_MyImpl(),
org.openoffice.MyService,
[optional my.implementation.name] );
If used as a global object, with a constructor that is executed when the
DLL is loaded, that won't
Hi Daniel,
IMO it doesn't matter whether you create that data (mostly the
implementation name) at the point of loading the library or slightly
later when the UNO service needs to be instantiated.
It might be everything from slightly later to never (because perhaps
sevice Foo from lib A is
Thorsten Behrens wrote:
Daniel Boelzle [EMAIL PROTECTED] writes:
I'd like to present/discuss a recent helper I have developed which IMO
simplifies the implementation of UNO services in C++ a lot.
[...]
So what do you think? Comments, please.
Great stuff! Always having to write so much
Hello,
I'd like to present/discuss a recent helper I have developed which IMO
simplifies the implementation of UNO services in C++ a lot.
Using the following (what I call) service declaration, the developer can
concentrate on implementing her service's interfaces, e.g.
class MyImpl :
