Re: API freeze break request: gtkmm: Gtk::Plug
- From: Billy O'Connor <billyoc gnuyork org>
- To: Elijah Newren <newren gmail com>
- Cc: gnome-release-team <release-team gnome org>, Murray Cumming <murrayc murrayc com>, gtkmm-list <gtkmm-list gnome org>
- Subject: Re: API freeze break request: gtkmm: Gtk::Plug
- Date: Mon, 24 Jan 2005 18:49:17 -0500
Elijah Newren <newren gmail com> writes:
> On Mon, 24 Jan 2005 20:25:16 +0100, Murray Cumming <murrayc murrayc com> wrote:
>> Dear GNOME release-team,
>>
>> Could we have 2 release-team API-freeze-break approvals for this small
>> gtkmm API addition please? It adds a default constructor, which takes no
>> arguments, so it can't really be wrong. It's needed by Coaster.
>>
>> http://bugzilla.gnome.org/show_bug.cgi?id=164935
>
> Looks simple and straightforward. 1 of 2.
>
>
> An off-topic comment/question, though. I noticed the following in the
> patch (in the "context" region):
>
> explicit Plug(const Glib::RefPtr<Gdk::Display>& display,
> GdkNativeWindow socket_id);
>
> Why would a constructor with more than one parameter need or want the
> explicit keyword (not that it hurts or anything, but I was just
> curious if I was missing something from the newer C++ standard or if
> somehow I missed an alternate use for the keyword somehow...)?
I thought that explicit would have an effect if a constructor has
multiple arguments and all but one of the arguments has a default
value.
--
Billy
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]