From e88c7b29ea9ec9fcd6ac6b15c965085152100d2e Mon Sep 17 00:00:00 2001 From: Stanislaw Halik Date: Sun, 18 Jun 2017 18:19:17 +0200 Subject: get rid of "volatile" abuse We heavily used "volatile bool" to check if the thread loop should stop. But this functionality is already provided by Qt5's QThread::requestInterruption. In other cases, "volatile" is wonderfully underspecified so it's better to ditch its usage in favor of std::atomic. At the time we don't appear to be using the "volatile" keyword except when calling win32's Interlocked*() family of functions as necessary. In freetrackclient's header the "volatile" qualifier was used as part of a typedef. This doesn't work. Use it as part of data declaration. --- logic/tracker.h | 1 - 1 file changed, 1 deletion(-) (limited to 'logic/tracker.h') diff --git a/logic/tracker.h b/logic/tracker.h index 2c4c5610..b1ed4042 100644 --- a/logic/tracker.h +++ b/logic/tracker.h @@ -40,7 +40,6 @@ struct bits f_enabled_h = 1 << 1, f_enabled_p = 1 << 2, f_zero = 1 << 3, - f_should_quit = 1 << 4, }; std::atomic b; -- cgit v1.2.3