summaryrefslogtreecommitdiff
path: root/README-hacking
diff options
context:
space:
mode:
authorAkim Demaille <akim.demaille@gmail.com>2018-09-06 14:07:12 +0200
committerAkim Demaille <akim.demaille@gmail.com>2018-09-08 07:01:50 +0200
commit41c43ef3d7e1b87ce478d85a1f06255f1dee72dd (patch)
tree95416c8321a4d8a50149291d4c1d2a0f92c5b0b3 /README-hacking
parent1dac131ec45ffa1e382319a94640c65bd10f6aa5 (diff)
downloadbison-41c43ef3d7e1b87ce478d85a1f06255f1dee72dd.tar.gz
CI: enable compiler warnings
* .travis.yml: here. * README-hacking: We no longer aim at K&R C.
Diffstat (limited to 'README-hacking')
-rw-r--r--README-hacking7
1 files changed, 2 insertions, 5 deletions
diff --git a/README-hacking b/README-hacking
index 56761c1c..01d44429 100644
--- a/README-hacking
+++ b/README-hacking
@@ -273,10 +273,7 @@ release:
- running "make maintainer-check-release" takes care of running
maintainer-check, maintainer-check-push and maintainer-check-xml.
-- Change tests/atlocal/CFLAGS to add your preferred options. For instance,
- "-traditional" to check that the parsers are K&R. Note that it does not
- make sense for glr.c, which should be ANSI, but currently is actually GNU
- C, nor for lalr1.cc.
+- Change tests/atlocal/CFLAGS to add your preferred options.
- Test with a very recent version of GCC for both C and C++. Testing with
older versions that are still in use is nice too.
@@ -294,7 +291,7 @@ In particular, be sure to read README-release.
week before a stable release, to give them time to translate them. Before
generating the *.pot files, make sure that po/POTFILES.in and
runtime-po/POTFILES.in list all files with translatable strings. This
-helps: grep -l '\<_(' *
+helps: grep -l '\<_(' *.
** Tests
See above.