1: -*- outline -*-
3: This file describes all the things left to do on GNU Forth. The list
4: is not complete, so you should add topics you miss or refine existing
5: topics. If you are working on a topic, add your name to the right of
6: the topic. If you have completed the work, remove the topic.
8: This an emacs outline. Use '*' to create topics.
10: *The Engine
11: **measure the effect of some variations on different machines:
12: direct/indirect, NEXT splitting, keeping the TOSses in variables
13: **make it easy to put the right variation for each processor into the
14: configuration. I.e., on installation all combinations of options
15: should be measured and the fastest chosen. Knowing OS and architecture
16: is not enough, the best options depend more on the processor and the
17: compiler version.
19: * ANSI Forth
20: Add the remaining words
22: *Run-time System
23: **Gender-independent image file format and loader
24: **Stack Checking using the MMU where the OS makes it possible.
27: ** Machines/OSs
28: VMS (VAX,AXP)
29: DOS 8088 (16-bit or 32-bit? Note: there are no far pointers in gforth,
30: so 16-bit means 64k max.)
36: Use gcc-generated assembly on machines without gcc, but with
37: processors supported by gcc
39: *Foreign Language Interface
40: If anybody wants to do this, take a look at
42: Some of the problems are discussed there,
44: Stuart Ramsden is doing a bit here.
48: *Windows and Graphics
49: **Ask Brian Dunn and Mike Hore for their OS-independent interface
50: **use the Foreign Language Interface to make X-Windows support
52: *Program Development Environment
53: Issues: Convenience, portability across plattforms, compatibility with
54: existing tools (Emacs, F-PC)
55: ** Decompiler and Debugger
56: need debugging
57: ** Profiling
58: The way this (and perhaps also debugging features) could work is this:
59: On compilation all code fields are remembered somewhere (using a
60: special hook like etags). If the user now decides to profile part of
61: the code, the corresponding code fields are replaced by fields
62: pointing to code that performs the measurement (or whatever else is
64: ** emacs support
65: can be improved
66: **prefix file generator
67: A tool for generating a prefix file for a program that explains in
68: what way the program conforms to ANSI (i.e., which wordsets are used)
69: and contains Forth definitions for the simple non-ANSI words.
70: ** rightcase
71: A tool that converts all uses of words in a source text to the exact
72: case of the definition. There's something like this out there on the
73: net (Joerg Plewe has posted a reference), but I think a program that
74: wires itself into the compiler (like etags.fs) is harder to fool by
75: search order tricks etc.
77: *Object-Oriented Extensions
78: John Hayes has a portable package
81: A texinfo file
82: ** a tool that extracts (stack) comments from forth sources and replaces
83: them in .ds files.
84: **glossaries of all wordsets.
85: *** Inclusion of stack comments, glossary comments, and wordset comments
86: in all source files.
88: * Distribution and Announcements
89: ** add copyright notices to all the source files
90: ** Write articles for (general-purpose) magazines