- view: text
- select for diffs
Tue Feb 16 06:32:28 1999 UTC
(23 years, 11 months ago) by crook
CVS tags: v0-5-0
-Added my name to the ToDo file under documentation
-Glossed the oof files
-Minor glossary additions elsewhere
-Another set of changes to gforth.ds; mainly the addition of material
to the introductory chapter. Also, re-organised stuff in the oof
sections and made a typo pass over a few other bits.
-*- outline -*-
This file describes all the things left to do on GNU Forth. The list
is not complete, so you should add topics you miss or refine existing
topics. If you are working on a topic, add your name to the right of
the topic. If you have completed the work, remove the topic.
This an emacs outline. Use '*' to create topics.
**measure the effect of some variations on different machines:
direct/indirect, NEXT splitting, keeping the TOSses in variables
**make it easy to put the right variation for each processor into the
configuration. I.e., on installation all combinations of options
should be measured and the fastest chosen. Knowing OS and architecture
is not enough, the best options depend more on the processor and the
* ANSI Forth
Add the remaining words
**Gender-independent image file format and loader
**Stack Checking using the MMU where the OS makes it possible.
DOS 8088 (16-bit or 32-bit? Note: there are no far pointers in gforth,
so 16-bit means 64k max.)
Use gcc-generated assembly on machines without gcc, but with
processors supported by gcc
*Foreign Language Interface
If anybody wants to do this, take a look at
Some of the problems are discussed there,
Stuart Ramsden is doing a bit here.
*Windows and Graphics
**Ask Brian Dunn and Mike Hore for their OS-independent interface
**use the Foreign Language Interface to make X-Windows support
*Program Development Environment
Issues: Convenience, portability across plattforms, compatibility with
existing tools (Emacs, F-PC)
** Decompiler and Debugger
The way this (and perhaps also debugging features) could work is this:
On compilation all code fields are remembered somewhere (using a
special hook like etags). If the user now decides to profile part of
the code, the corresponding code fields are replaced by fields
pointing to code that performs the measurement (or whatever else is
** emacs support
can be improved
**prefix file generator
extend or complement ans-report.fs to provide Forth definitions for
the simple non-ANSI words.
A tool that converts all uses of words in a source text to the exact
case of the definition. There's something like this out there on the
net (Joerg Plewe has posted a reference), but I think a program that
wires itself into the compiler (like etags.fs) is harder to fool by
search order tricks etc. EVALUATE is a problem.
*Documentation (Neal Crook, firstname.lastname@example.org is working on this)
A texinfo file
**glossaries of all wordsets.
*** Inclusion of stack comments, glossary comments, and wordset comments
in all source files.
* Distribution and Announcements
** Write articles for (general-purpose) magazines