summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorJim Blandy <jimb@red-bean.com>1998-07-29 18:34:59 +0000
committerJim Blandy <jimb@red-bean.com>1998-07-29 18:34:59 +0000
commit99be34501819711fe56f8bce73f0a2a075dd77ca (patch)
treec2a2dad0c6b2b0acfc45f775c84a72559b0e01d1 /HACKING
parentd2bd3d8dceae0b0e612d85086da8dcca35c98716 (diff)
downloadguile-99be34501819711fe56f8bce73f0a2a075dd77ca.tar.gz
* 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... :(
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING7
1 files changed, 7 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index da966fc63..f0b34d01d 100644
--- a/HACKING
+++ b/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: