*** empty log message ***

1 files changed, 6 insertions, 4 deletions

diff --git a/HACKING b/HACKING
index 330782fd5..3c26791c0 100644
--- a/HACKING
+++ b/HACKING
@@ -86,14 +86,16 @@ make-stds.texi.
 - The Guile tree should compile without warnings under the following
 GCC switches, which are the default in the current configure script:
     -O2 -Wall -Wpointer-arith -Wmissing-prototypes
-The only exceptions are the warnings about variables being clobbered
-by longjmp/vfork in eval.c.  (Tho' if you can figure out how to get
-rid of those, too, I'd be happy.)
+The only warnings which can be tolerated are those about variables
+being clobbered by longjmp/vfork in eval.c.  The variables in question
+are critical to the interpreter's performance; as far as I can tell,
+it is difficult/annoying to avoid these warnings without slowing the
+system down substantially.  (If you can figure out a good fix, I'd be happy to see it.)
 
 Note that the warnings generated vary from one version of GCC to the
 next, and from one architecture to the next (apparently).  To provide
 a concrete common standard, Guile should compile without warnings from
-GCC 2.7.2.3 in a Red Hat 5.0 i386 Linux machine.  Furthermore, each
+GCC 2.7.2.3 in a Red Hat 5.2 i386 Linux machine.  Furthermore, each
 developer should pursue any additional warnings noted by on their
 compiler.  This means that people using more stringent compilers will
 have more work to do, and assures that everyone won't switch to the