Re: [gtkmm] Re: [sigc] Imminent libsigc++ 1.2 API freeze



> Just to make clear: it works like so:
> 
> int foo();
> Signal0<void> signal0;
> signal0.connect(retype_return<void>(slot(&foo)));
> 
> Not very intuitive at first sight but easy to remember once you got it.
> We could add a stub hide_return() that does exactly the same, though.

Ah, in that case there's no need to.
But really, SigC++ NEEDS better docs.

Jarek


----------------------------------------------------------------------
Zanim zaczniesz swoj dzien... >>> http://link.interia.pl/f1628





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]