2017-June Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
ANNOUNCE: gtkmm 3.22.0,
Murray Cumming
ANNOUNCE: glibmm 2.52.0,
Murray Cumming
Why do Glib::ustring::operator[] and at() return values, not references?,
Daniel Boles
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Chris Vine
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Chris Vine
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Daniel Boles
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Chris Vine
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Daniel Boles
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Jonathan Wakely
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Daniel Boles
- Re: Why do Glib::ustring::operator[] and at() return values, not references?,
Daniel Boles
Gtk::Application::get_default segfault on exit,
David Mugnai
<Possible follow-ups>
Re: Gtk::Application::get_default segfault on exit,
aitor_czr
Re: Making use of move semantics?,
Murray Cumming
C++17's string_view (was Re: Making use of move semantics?),
Murray Cumming
Re: Compile/link errors with glibmm-2.4 build using jhbuild,
Kjell Ahlstedt
Mail converted by MHonArc
