blob: 34caddedb60a7a4cd35ae3df9064da2cc1401cc7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
* resolve the items in the to.do directory
** expand the above into individual requests and handle those requests
* the manual:
** integrate the items in the faqs/ directory into the manual or code
or similar
*** create a section on flex design, features, etc.
**** we're not adding comments between pattern-action rules; explain
why in the documentation
** We've converted the flex manual to texinfo, but some issues remain:
** index flex.texi
** think about dividing flex.texi into more sections and subsections
** Have flex.texi use automakes version info.
** the pro-.man crowd will want a manpage; I don't want to maintain
one. What to do? help2man, possibly.
*** jason@thought.net notes that a short description of flex, a
summary of command line options and a reference to the info pages will
probably satisfy the need for a man page
* repackage the distribution
** address lex-replacement: document or provide an option through
configure for creating lex and libl.a files
** gettextify flex
* test suite
** Rewrite tests/Makefile.in and friends so that users do not need to
alter it when they add tests
** make test suite more complete
** create a script which sets up a new skeleton test directory with a
correct .cvsignore file and other such niceties
** explicitly describe the copyright state of the entries in
tests/. millaway has assigned the rights to the test suite to me
and so the test suite will be under the flex license.
* move as much skeleton code as possible out of gen.c and into
flex.skl
* create a uniform memory management API
* figure out whether we want to add the capability to have
auto-generated backout rules
* C++
** revisit the C++ API. We get requests to make it more complete.
|
