httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Max Kellermann <...@duempel.org>
Subject Re: [PATCH] first snapshot of my "let's kill void*env" patch
Date Tue, 11 Jan 2005 09:54:49 GMT
On 2005/01/11 05:26, Randy Kobes <randy@theoryx5.uwinnipeg.ca> wrote:
> Thanks ... For future reference, what version, and options, for gcc
> do you use to enable these warnings about declarations being done
> too late (for some compilers, like Win32 Visual Studio)?  This
> question has also come up with mod_perl.

I use the following gcc versions:

gcc version 3.3.5 (Debian 1:3.3.5-6)
gcc version 3.4.4 20041218 (prerelease) (Debian 3.4.3-6)

gcc 3.4 introduces the option "-Wdeclaration-after-statement", but I
did not use it, I found out about it a few minutes ago.

Although declarations are officially allowed in the middle of a
function with C99, I never use it.

My "standard" set of warning flags is:

-std=gnu99 -Wall -W -Wmissing-prototypes -Wwrite-strings -Wcast-qual
-Wfloat-equal -Wshadow -Wpointer-arith -Wbad-function-cast
-Wsign-compare -Waggregate-return -Wmissing-declarations
-Wmissing-noreturn -Wmissing-format-attribute -Wpacked
-Wredundant-decls -Wnested-externs -Winline -Wdisabled-optimization
-Wno-long-long -Wstrict-prototypes -Wundef -pedantic-errors -Werror

.. but I havn't revised it for gcc 3.4 yet. I will try to compile
apreq with as many as possible. What about adding warning flags to the
apreq makefiles?

Max


Mime
View raw message