|
1 for RCOMP resource compiler. |
|
2 |
|
3 |
|
4 1. Major but arguably cosmetic: |
|
5 |
|
6 Redesign and rewrite command line processing to provide a more |
|
7 friendly verb with meaningful qualifiers. |
|
8 |
|
9 Call the preprocessor internally and make it possible to do away with |
|
10 a batch command framework. |
|
11 |
|
12 2. Niggling little fixes: |
|
13 |
|
14 -v is TOO verbose. Provide a log file capability for this and make -v |
|
15 simply provide terse status and version messages. |
|
16 |
|
17 The current verb produces useless error messages when the expected |
|
18 parameters are missing. This could be done in a much better way. |
|
19 |
|
20 Improve the build procedures so that they work first time from the |
|
21 command line. Currently, the command line build fails because of |
|
22 the way LEX/YACC source code is generated which then forms part of |
|
23 the rest of the build. |
|
24 |
|
25 3. Major but of possible strategic importance: |
|
26 |
|
27 Generate linkable binary resources. |
|
28 |
|
29 Generate linkable object file to satisfy external references to |
|
30 resource IDs instead of generating a header file. |
|
31 |
|
32 4. Problem fixes |
|
33 |
|
34 The whole code is defective in that it misuses assert as a status |
|
35 checking mechanism. |
|
36 |
|
37 Lots of little defects in the code about array assumptions etc. |
|
38 |
|
39 Make Unicode the internal character set of RCOMP, LEX and YACC. |
|
40 (You know, during an idle lunchtime) |
|
41 |
|
42 5. RCOMP language feature changes |
|
43 |
|
44 Review the language with language design experts. |
|
45 |
|
46 If there are unsatisfied forward references, the compiler fails to |
|
47 report intervening syntax errors and instead complains about |
|
48 "link name not found". Can this be fixed? |
|
49 |
|
50 |
|
51 |
|
52 Specifically for version 3.15: |
|
53 =================================== |
|
54 |
|
55 |
|
56 . Implement actal mapping code for all character set types to unicode. |
|
57 |