On Tue, 2015-06-30 at 12:18 +0100, Chris Vine wrote: [snip] > However, I don't think this should have any bearing on whether gtkmm > adopts C++11. As I have mentioned, this should not and does not > depend > on what ABI a particular distribution happens to choose for its C++ > binaries.
Using C++11 in gtkmm for anything interesting will lead to an ABI break - apps that have been built against gtkmm will stop running when their gtkmm is replaced with out C++11 gtkmm. If we can be fairly sure that an ABI break will happen on the main distros anyway, then we can go ahead with the break in gtkmm knowing that nobody can blame us for the ABI break. There are other small ABI breaks that we'd like to make, unrelated to C ++11. So for simplicity, we could ignore "use of C++11 features" when deciding whether to break ABI in gtkmm, though it's superficially going to look like C++11 is the big change. -- Murray Cumming murr...@murrayc.com www.murrayc.com _______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
