Re: get/set wrap methods.

[Pavlo Solntsev <pavlo solntsev gmail com>]

Thanks for comments.  My macroses:

  _MEMBER_GET(name,name,const Glib::ustring&,const gchar*)
  _MEMBER_SET(name,name,Glib::ustring,gchar*)

the generated code :
const Glib::ustring& DsnInfo::get_name() const
{
  return Glib::convert_const_gchar_ptr_to_ustring(gobj()->name); // This is my concern. it looks like we return ref for temp object
}

void DsnInfo::set_name(const Glib::ustring& value)
{
  gobj()->name = g_strdup((value).c_str());
}

Thanks.

-Pavlo Solntsev

---------------------------------------------------------------------------------------------

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

On Thu, Feb 22, 2018 at 12:34 PM, Daniel Boles <dboles src gmail com> wrote:

On 22 February 2018 at 18:32, Daniel Boles <dboles src gmail com> wrote:

also, I don't see how RefPtr is relevant to the given example struct; it's only for Glib::Object instances, i.e. things that themselves wrap GObjects, as RefPtr is implemented via GObject refcounts.

...in the currently stable glibmm, at least. Beyond that, in the next release, it'll be an std::shared_ptr, layering a different layer of refcounting over GObject's own.

but the point stands: what would a RefPtr to a char* or any other simple property type even mean? They should just be returned by value, not by reference.

_______________________________________________
gtkmm-list mailing list
gtkmm-list gnome org
https://mail.gnome.org/mailman/listinfo/gtkmm-list