Den 2015-08-30 kl. 11:34, skrev Murray Cumming:
On Sat, 2015-08-29 at 17:53 +0200, Jonas Platte wrote:
Most destructors are noexcept(true) by default in C++11 already [1].
If some class in *mm has a destructor that can throw exceptions, it's
likely to be broken already.
[1]:
Am 30.08.2015 um 11:34 schrieb Murray Cumming:
On Sat, 2015-08-29 at 17:53 +0200, Jonas Platte wrote:
Most destructors are noexcept(true) by default in C++11 already [1].
If some class in *mm has a destructor that can throw exceptions, it's
likely to be broken already.
[1]:
On Sat, 2015-08-29 at 17:53 +0200, Jonas Platte wrote:
Most destructors are noexcept(true) by default in C++11 already [1].
If some class in *mm has a destructor that can throw exceptions, it's
likely to be broken already.
[1]: http://en.cppreference.com/w/cpp/language/destructor
Thanks.
On Sat, 2015-08-29 at 13:37 -0700, Andrew Potter wrote:
On Wed, Aug 26, 2015 at 1:20 PM, Murray Cumming murr...@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?
On Sun, 30 Aug 2015 12:34:30 +0200
Murray Cumming murr...@murrayc.com wrote:
We could probably require C++14 for the next glibmm version (2.47/48).
That would require gcc-4.9 or later, which supports the -std=c++14
flag and also shared mutexes (read-write locks). That doesn't mean it
shouldn't
