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

[MHL Schulze t-online de (Martin Schulze)]

Am 24.07.2002 22:36 schrieb(en) Murray Cumming:
> On Wed, 2002-07-24 at 21:26, Martin Schulze wrote:
> > Am 24.07.2002 21:46 schrieb(en) Murray Cumming:
> > > On Wed, 2002-07-24 at 20:32, Jarek Dukat wrote:
> > > > > Actually I think you want SigC::bind_return().
> > > >
> > > > No. Bind return can't bind `bool foo();' to `void foo()', it works
> in
> > > > reverse situation.
> > >
> > > That would be hide_return(), I think. I don't think we have that.
> > > Something for  libsigc_extras.
> >
> > 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.
>
> So Jarek is wrong and bind_return _can_ do what he wants?

No, retype_return can do what he wants! retype_return is _not_ bind_return!
Maybe things will get clearer after a good sleep :-)
> --
> Murray Cumming
> murrayc usa net
> www.murrayc.com