gpre C++ compiler warnings with GCC 4.4.1 [CORE3022] #3403
Labels
affect-version: 2.0.0
affect-version: 2.0.1
affect-version: 2.0.2
affect-version: 2.0.3
affect-version: 2.0.4
affect-version: 2.0.5
affect-version: 2.0.6
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.1.3
affect-version: 2.5 Alpha 1
affect-version: 2.5 Beta 1
affect-version: 2.5 Beta 2
affect-version: 2.5 RC1
affect-version: 2.5 RC2
affect-version: 2.5 RC3
affect-version: 2.5.0
affect-version: 3.0 Initial
fix-version: 2.0.7
fix-version: 2.1.4
fix-version: 2.5.1
fix-version: 3.0 Alpha 1
priority: minor
qa: cannot be tested
type: bug
Submitted by: @AlexPeshkoff
Attachments:
AmbigiousElseWarning.patch
Issue was reported and patch provided by Daniel Dodson <mailto:zabbit@yahoo.com>
When compiling generated C++ from gpre I was receiving a warning "ambiguous else statement". From the following kind of statement...
it was outputting, in part, the following code
Legally I don't think this is a problem because the else statement applies to the nearest 'if' statement (so the second one in this case). However I didn't want to add a rule to ignore this warning because that would be bad practise in hand crafted C++ and I would want it highlighted. So rather than add a rule for different flags I decided to modify gpre so that the following is produced...
Commits: f126fd5 800d801 e562c8f a233141
The text was updated successfully, but these errors were encountered: