[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#23771: Eliminating compiler warnings

From: Richard Stallman
Subject: bug#23771: Eliminating compiler warnings
Date: Wed, 15 Jun 2016 16:24:51 -0400

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > I would like to get rid of all compiler warnings in the Cygwin builds 
  > (X11, w32, and nox).  There are currently none in the X11 build, but 
  > there are a lot in the other builds.

It could be that the best way to get rid of some of these warnings
is to delete some -W option that causes GCC to issue them.

In the case of _Noreturn, isn't there a simpler approach,
defining a macro that expands into either _Noreturn or nothing?
Or defining _Noreturn as a no-op when there is no other definition?

  >        int fringe_bitmap;
  > +#endif

Surely it is easier to put in some code that will
unconditionally use that variable.  But maybe just delete
the -W option that causes these warnings.

To clutter up the code to placate a finicky compiler is a change
for the worse.  If the compiler is so finicky only because a special
option asked it to be, why be massochistic?

Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]