* configure.in: Request more warnings.

* configure: Regenerated.
* HACKING: Ask people not to make changes that introduce those
warnings.  Now I have to go through the code and actually bring it
up to standards... :(

HACKING

@@ -57,6 +57,13 @@ GNU coding standards.  The standards are available via anonymous FTP
 from prep.ai.mit.edu, as /pub/gnu/standards/standards.texi and
 make-stds.texi.
 
+- The Guile tree should compile without warnings under the following
+GCC switches, which are the default in the current configure script:
+    -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes
+The only exceptions are the warnings about variables being clobbered
+by setjmp/longjmp in eval.c.  (Tho' if you can figure out how to get
+rid of those, too, I'd be happy.)
+
 - When you make a user-visible change (i.e. one that should be
 documented, and appear in NEWS, put an asterisk in column zero of the
 start of the ChangeLog entry, like so:

configure

@@ -4381,7 +4381,8 @@ fi
 
 ## If we're using GCC, ask for aggressive warnings.
 case "$GCC" in
-  yes ) CFLAGS="$CFLAGS -Wall -Wpointer-arith" ;;
+  yes )
+    CFLAGS="$CFLAGS -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes" ;;
 esac
 
 for ac_prog in mawk gawk nawk awk
@@ -4389,7 +4390,7 @@ do
 # Extract the first word of "$ac_prog", so it can be a program name with args.
 set dummy $ac_prog; ac_word=$2
 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:4393: checking for $ac_word" >&5
+echo "configure:4394: checking for $ac_word" >&5
 if eval "test \"`echo '$''{'ac_cv_prog_AWK'+set}'`\" = set"; then
   echo $ac_n "(cached) $ac_c" 1>&6
 else

configure.in

@@ -372,7 +372,8 @@ fi
 
 ## If we're using GCC, ask for aggressive warnings.
 case "$GCC" in
-  yes ) CFLAGS="$CFLAGS -Wall -Wpointer-arith" ;;
+  yes )
+    CFLAGS="$CFLAGS -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes" ;;
 esac
 
 AC_PROG_AWK