🚀 go-pugleaf

I've recently observed some free software authors use the
justification "it shuts up gcc" when asked why they declare main() as
void.  (Presumably, they're using -Wall).  Since "void main" is not
correct according to ANSI, I would appreciate it if the next version
of gcc could warn about it.  I would advocate warning about it in all
cases, but warning about it only when -Wall is set is fine.

	/* test1.c: warns if compiled with -Wall */
	int main()
	{
	}

	/* test2.c: does not warn even if compiled with -Wall */
	void main()
	{
	}

Thanks.