From 99bb3328c368663d086115c58fd22f255518ea25 Mon Sep 17 00:00:00 2001 From: sbruno Date: Fri, 25 Oct 2013 01:10:07 +0000 Subject: Queisce quite a few clang warnings -Wdangling-else due to this work around for compiling gperf under Visual Studio from 1998. ref. http://msdn.microsoft.com/en-us/library/b80153d8%28v=vs.90%29.aspx ref. http://stackoverflow.com/questions/984878/what-is-the-possible-use-for-define-for-if-false-else-for --- contrib/gperf/src/search.cc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'contrib/gperf/src') diff --git a/contrib/gperf/src/search.cc b/contrib/gperf/src/search.cc index c245970..956b5be 100644 --- a/contrib/gperf/src/search.cc +++ b/contrib/gperf/src/search.cc @@ -36,7 +36,10 @@ /* ============================== Portability ============================== */ /* Assume ISO C++ 'for' scoping rule. */ -#define for if (0) ; else for +/* This code is used to work around scoping issues with visual studio 6 from + * 1998. Comment it out here to queisce numerous -Wdangling-else warnings + * from clang. +#define for if (0) ; else for */ /* Dynamically allocated array with dynamic extent: -- cgit v1.1