|
996
|
1 This list applies to all the optional modules one can install for CLC-INTERCAL,
|
|
|
2 not just to the Base package. It would be better to split this list and have
|
|
|
3 each item listed in the most relevant package.
|
|
|
4
|
|
|
5 The following files are intended to be in the distribution but have not
|
|
|
6 been included in this pre-escape:
|
|
|
7
|
|
|
8 IPv6 support in INTERNET library (this has, however, been designed,
|
|
|
9 and will appear in the documentation in the near future).
|
|
|
10 Language/INTERCAL.pm (no longer needed, but useful for compatibility)
|
|
|
11 bin/oo,\ ick (ditto -- use bin/sick)
|
|
|
12 Language/INTERCAL/Backend/Uncompile.pm - attempt to get INTERCAL source
|
|
|
13 by any means possible: if the object has some source code, it is
|
|
|
14 extracted; any compiled code without a source is disassembled.
|
|
|
15 doc/examples/computed-labels.li (try "(.1) DO .1 <- #1 ... PLEASE COME FROM (1)")
|
|
|
16 doc/examples/next-from.i (if you never used NEXT FROM do it now!)
|
|
|
17 doc/examples/quantum/next-from.i
|
|
|
18 more doc/examples/*.i
|
|
|
19 some of the test scripts (which will say "Skipped: not implemented"
|
|
|
20 or words to that effect during "make test"); also, some of the
|
|
|
21 ones provided could do with more tests
|
|
|
22
|
|
|
23 The following are known bugs:
|
|
|
24
|
|
|
25 using intercalc --line, command completion works but shows a weird list
|
|
|
26 of possible completion if there is more than one match; this is
|
|
|
27 because the completion variables described in the readline
|
|
|
28 documentation don't have the effect described there.
|
|
|
29 using quantum statements in the calculator can produce unexpected results
|
|
|
30 events defined in the calculator don't work (of course, they work in sick)
|
|
|
31 reloading the compiler while using the calculator is fully supported, for
|
|
|
32 example to switch between 'sick' and 'ick'; however at present changes
|
|
|
33 made to the compiler before reloading do not correctly propagate to
|
|
|
34 the reloaded compiler: the correct behaviour is to reapply all changes
|
|
|
35 to the new compiler, taking into account the fact that the new compiler
|
|
|
36 may be completely different from the old one. This is not as simple as
|
|
|
37 it sounds.
|
|
|
38
|
|
|
39 The following functionality is missing:
|
|
|
40
|
|
|
41 The documentation is not currently installed by "make install"; moreover,
|
|
|
42 there is no Makefile target to install it.
|
|
|
43 Politesse checking
|
|
|
44 The user interfaces work with intercalc but are not yet powerful enough
|
|
|
45 for use with sick.
|
|
|
46 The optimiser (optimise.iacc is provided, empty, as a placeholder)
|
|
|
47 Additionally, "iacc.iacc" (and "iacc.io") do not currently provide
|
|
|
48 syntax to create optimisers (you can, of course, write your own
|
|
|
49 extensions for that)
|
|
|
50 Interface-specific configuration in sickrc
|
|
|
51 The Curses interface requires some sort of scrollbars. It works fine if
|
|
|
52 the top window fits in the screen, but makes a mess if it doesn't.
|
|
|
53 In a standard 80x25 terminal this means: oic yes, anything else no.
|
|
|
54 The X interface also needs some sort of scrollbars, but this is not as
|
|
|
55 urgent as the problem only appears with a large text window, such as
|
|
|
56 the trace window after a few commands are traced, or the history
|
|
|
57 window after a lot of commands.
|
|
|
58 The compiler could be made to do a lot more work at compile time, leaving
|
|
|
59 less for the runtime. For example, if a program contains CREATE
|
|
|
60 statements, it is possible to avoid recompilation at runtime in most
|
|
|
61 cases, by recompiling the program with the extended grammar but
|
|
|
62 recording that the new rules introduced are not enabled. See function
|
|
|
63 find_code in Language::INTERCAL::Object to see why this would work.
|
|
|
64 Maybe this could be enabled only if optimisation is requested.
|
|
|
65 Related to the previous point, the compiler compiler just stores the list
|
|
|
66 of CREATE statements necessary to recreate the compiler when a user
|
|
|
67 program is compiled. This could be improved by running the code
|
|
|
68 generated by the compiler compiler and storing the completed grammar.
|
|
|
69 However this turns out to be a small fraction of the compile time, so
|
|
|
70 it isn't a priority to do anything about that.
|
|
|
71
|
|
|
72 Patches to implement any of the above will be gratefully received: please
|
|
|
73 email them to intercal@sdf.lonestar.org, including the word INTERLEAVING in
|
|
|
74 the subject (or the message may be ignored as spam). Please specify whether
|
|
|
75 you wish your contribution to remain anonymous, and if not, what name do
|
|
|
76 you want to be added to the CLC-INTERCAL hall of shame.
|
|
|
77
|
