Re: [dbus-cplusplus-devel] contributing a submission to the project...best way?

[Andreas V. <li...@br...>]

Am Tue, 10 Nov 2009 12:28:19 -0800 schrieb Freyensee, James P:

> A co-worker of mine just submitted bug 25022 that contains our
> addition to the project.  We verified the merge (from freedesktop)
> works, at least for the product we are using with it.  We did not see
> a category for "dbus-c++" so we filed it under "dbus" but stuck
> "dbuc-c++" in the Title. 

I applied some part of the patch. We could discuss about parts I didn't
yet apply (in the lib):

examples:
- op-cp
- op-signal
- most example modifications (I didn't yet look into it to deep)

connection.h/connection.cpp:

extern DXXAPI Dispatcher* default_dispatcher;

...and all changes specific to the change that Connection constructors
have a new parameter Dispatcher* dispatcher.

I've a raw idea what's the reason for it. But could you explain what
was the main idea behind this change.

connection.h/connection.cpp:
set_timeout()/get_timeout() stuff
-> applied


eventloop.cpp:
DefaultMutex::DefaultMutex()
{
	
	 	pthread_mutex_t recmutex = PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP; 
 	_mutex = recmutex;
	//_mutex = PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP;
	//pthread_mutex_init(&_mutex, NULL);
}

What was the reason of doing this?

The rest of the eventloop integration is applied now.

generate_adaptor.cpp/generate_proxy.cpp/generator_utils.cpp:

What are exactly the reason of these change? Looks for me like some sort
of Async method support. Could you spend some more words here?

regards
	Andreas