RFC: Avoiding #warning (C/C++ preprocessor extension)

[Mirko Boehm]

On Monday 31 October 2005 23:15, Nicolas Goutte wrote:
> > I would
> > say that no release tarball should contain -Werror.  It may be useful
> > during development but it would be unnecessarily painful for release.
>
> ... so you cannot even have it in development, except if everybody would
> use the same gcc version.
Why not? It can be used as a standard during development, and removed before 
the release. 

On the other hand, I do not see the point. Removing annoying "unused 
parameter" warnings should be a habit, no need to make the compiler barf at 
the first point where it encounters it. What is wrong with letting make 
finish the compile, and then removing all the warnings at once?

Forcing -Werror is too much of an annoyance, I think.

--Mirko.
-- 
KDE e.V.: http://ev.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051101/f4c270d1/attachment.sig>