🚀 go-pugleaf

(I'm using the NYU internal version of gcc for the ibm rt pc, if it matters).

If I compile with -Wall, I get warnings about else statements with
empty bodies, e.g.

	if (expr)
		f();
	else	;

In my case the empty body is generated by a macro.

1) 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?

2) Is there a way to turn them off, and still keep -Wall?

3) I can suppress them by using a null inline function, like

	static inline void null() { }

   and change my macro to evaluate to null(); is there a better way?


Jan Edler
NYU Ultracomputer Research Laboratory
edler@nyu.edu