TODO


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
62
63
64
65
66
67

* 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 (millaway is working on this; much of the FAQS directory
  is old or uninformative)

*** create a section on flex design, features, etc.

* address lex-replacement: document or provide an option through
   configure for creating lex and libl.a files (but remember this has
   posix implications)

* getext

** update gettext support from gettext-0.11 to gettext-0.11.2 %%

** make sure all flex modules use gettext translation facilities

*subdirectories

** in examples/manual, integrate the Makefile.examples into the
    Makefile.am

* test suite

** make test suite more complete

*** add a test for the --posix option %%

** 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.

* generic coding

** pay attention to the POSIXLY_CORRECT variable (this is from the GNU
   coding standards and is a good idea) %%

** 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.

* build system

** use bootstrapper

Legend:

*, **, ***: outline depth
%% at end of item: must be adressed before next major release

Local Variables:
Mode: text
mode: outline-minor
End: