🚀 go-pugleaf

> If I compile with -Wall, I get warnings about else statements with
> empty bodies, e.g.
> 
> 	if (expr)
> 		f();
> 	else	;
> 
> ...These warnings don't seem very useful to me; am I missing something?
> Is there a common error that will be caught by the warning?

The "common" error caught by the code generating the above message is...
	if (expression);
		statement;
...where the extra semicolon at the end of the first line results in
"statement" being executed unconditionally.  The "else" case is designed to
guard against the less-common...
	if (expression);
		statement;
	else; if (expression2)
		statement2;
	else	statement3;

On the system here at least, you can eliminate the warning by having the
macro generate code in the form...
	if (expr)
		f();
	else	{}
-- 
		1972:  Canada has no Saturn V equivalent
		1990:  Canada has no Saturn V equivalent
	Arthur David Olson   ado@alw.nih.gov   ADO is a trademark of Ampex.