From cdd1de0854c5fd55f7e99c5546ccf7a7245927f5 Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Mon, 8 Apr 2013 11:23:53 +0300 Subject: Check for the C++11 "final" specifier and introduce SAL_FINAL I think it is useful to use SAL_FINAL mainly as a documentation aid, to make it clear to a code reader when a class is not expected to be derived from, and when a virtual function is not expected to be overridden in a derived class. Possibly there is also some class of bugs that using SAL_FINAL will help find? Change-Id: I45002f020dcb52e8a9f2962ff98780f2b80627af --- config_host/config_global.h.in | 1 + 1 file changed, 1 insertion(+) (limited to 'config_host') diff --git a/config_host/config_global.h.in b/config_host/config_global.h.in index 19b13dc2061f..02e284f9d6c1 100644 --- a/config_host/config_global.h.in +++ b/config_host/config_global.h.in @@ -14,6 +14,7 @@ Any change in this header will cause a rebuild of almost everything. #define HAVE_CXX11_DELETE 0 #define HAVE_CXX11_OVERRIDE 0 +#define HAVE_CXX11_FINAL 0 #define HAVE_CXX11_PERFECT_FORWARDING 0 #define HAVE_GCC_BUILTIN_ATOMIC 0 #define HAVE_GCC_PRAGMA_DIAGNOSTIC_MODIFY 0 -- cgit