Re: Re: interthread communication library "sigx++" (crossposting)

["Milosz Derezynski" <internalerror gmail com>]

Hey Klaus,

Before you officially package it I still want to change the open_tunnel() API - in case you didn't need it yet it's because sigx++ does it normally under the hood. But it belongs to the public API and it's not good to change it later as I don't want to change the major version already at the very beginning. It would be great if you could help me to find a naming for those taking an explicit dispatchable.

Ok, and as soon as a name strucks me i'll post it to the list, i haven't thought about it yet (maybe someone else has?)
 

Well, the assertion facilities moved from gmessages.h to gtestutils.h as I've just found out. The question is how to fix this - do you need backward compatibility or should sigx++ depend on glib-2.16?

Personally i think backwards compatibility could be good; looks like a bad move from glib's side to change this.
 

> - There is no way to specify an own compiler with the build system; one
> fried of mine has problems building it with g++ 4.2.1, he's installed 4.3
> but has no way to point the build to it

I'll include this possibility.

Thanks
 

> - A link to an SCM repository of sigx would be really nice

I know, I'm missing a SCM, too. I'm thinking about sourceforge.net, berlios.de or google - do you have a good suggestion?

We had bad experiences with berlios in the past (server downtimes for long time), SourceForge can be problematic too but it's proven, i think google code is very reliable (having past experiences with berlios and sourceforge i'd just choose Google Code these days).

> OK, it's a little lot at one time but you've gained some popularity here
> among a group of my friends because the library really rocks! It would be
> nice if you could fix the above problems, if you have the time.

Thanks for your appreciation! I will fix those things as soon as possible as I'm interested to have the library up and running, too.


--
Klaus