3 Tell <bug-m4@gnu.org> if you feel like volunteering for any
4 of these ideas, listed more or less in decreasing order of priority.
7 - Update documentation from accumulated mail about it
8 - Study synclines at the very beginning of each diverted sequence
9 - Make eval work on bignums - the 32 bits limit is artificial
10 From Krste Asanovic <krste@icsi.berkeley.edu>, 1993-03-20
12 * Optimization and clean up
13 - Check for memory leaks and uninitialized reads
14 From Vern Paxson <vern@horse.ee.lbl.gov> on 1993-12-06
15 - Profile GNU m4 and speed it up
16 From David J. MacKenzie <djm@eng.umd.edu>, 1993-01-20
18 GNU m4 should be sped up by a factor of three for competing
19 with other versions (I think that the lexer is not agressive
20 enough and too often return single characters; obstacks might
21 be a little abused, too).
22 - Have NULs go really undisturbed through GNU m4
23 See `dumpdef' and debugging section, which abuses %s
24 From Thorsten Ohl <ohl@chico.harvard.edu>, 1992-12-21
26 path.c (add_include_directory): Why the '\0' terminator?
28 GNU m4 is lousy regarding NULs in streams (this would require
29 maintaining the string lengths, and avoiding strlen, strcpy,
34 outline-regexp: " *[-+*.] \\|
\f"