Re: C++11: Deprecate Glib::Threads

[Murray Cumming <murrayc murrayc com>]

On Sun, 2015-08-30 at 12:34 +0200, Murray Cumming wrote:
> On Sat, 2015-08-29 at 13:37 -0700, Andrew Potter wrote:
> > On Wed, Aug 26, 2015 at 1:20 PM, Murray Cumming <
> > murrayc murrayc com> wrote:
> > > I'm starting to learn about the new concurrency APIs in C++11. I
> > > wonder
> > > if we could soon deprecate Glib::Threads, which wraps the glib
> > > threads
> > > API. Thoughts?
> > > https://developer.gnome.org/glibmm/stable/group__Threads.html
> >
> > Keep in mind Reader/Writer locks are only in C++14; do the current
> > major distros stable versions have a GCC new enough that users
> > could
> > update their code to avoid the depreciation warning?
>
> We could probably require C++14 for the next glibmm version
> (2.47/48).
> Would that then be enough to deprecate all of Glib::Threads?
>
> It's a little late in the glibmm 2.45/46 development cycle for such a
> big deprecation anyway. But we can already begin experimenting with
> replacing Glib::Threads stuff with C++11 API in our applications and
> documentation. For instance:
> https://git.gnome.org/browse/gtkmm-documentation/tree/examples/book/m
> ultithread 

Let's deprecate Glib::Threads for glibmm 2.48 (the next one):
https://bugzilla.gnome.org/show_bug.cgi?id=757674




-- 
Murray Cumming
murrayc murrayc com
www.murrayc.com