egcs-980129, fixed ambiguous `else' warnings in the gcc/f/ dir.

[Kaveh R. Ghazi]

 > From: Bernd Schmidt <crux@Pool.Informatik.RWTH-Aachen.DE>
 > 
 > >  > Coding style aside, the warning tells you that it is ambiguous when
 > >  > it is not.  If the tree is full, there is exactly one way it can be
 > >  > parsed.  Thus, a bug, IMO.
 > >  > r~
 > > 
 > >       Okay, then we should leave in all of them until its fixed.  That
 > > way when the fix is in, we see that the ones that should be noisy are
 > > still there and the ones that should be quiet are gone. 
 > > 
 > >       Is anyone (the original author) working on this?
 >  
 > I'll submit a fix for this on Monday.
 > Bernd

	Lot's of gcc's warnings emit diagnostics about things that are
coding style issues, not actual problems.

	So given that the GNU coding standards mention this particular
case, perhaps whatever fix you decide on should simply change the
wording but still say something even when an if-then-else tree is full. 
I recommend "Suggest braces around nested if-then-else." or something
similar. 

	This would be similar to the suggestion for parens around
assignments used as truth values. 

		--Kaveh
--
Kaveh R. Ghazi			Project Manager / Custom Development
ghazi@caip.rutgers.edu		ICon CMT Corp.