--- gforth/ToDo	1994/10/03 18:24:00	1.2
+++ gforth/ToDo	2001/05/07 12:04:44	1.10
@@ -7,26 +7,23 @@ the topic. If you have completed the wor
 
 This an emacs outline. Use '*' to create topics.
 
+* "DOS" Distribution
+eventually convert all text files LF -> CR LF
+check on 8.3 filenames?!
+
 *The Engine
 **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 otions depend more on the processor and the
+is not enough, the best options depend more on the processor and the
 compiler version.
 
 * ANSI Forth
 Add the remaining words
 
-* Configuration
-We should have a config script so people don't need to edit the
-Makefile etc.
-
 *Run-time System
-**startup.fs takes too long to load.
-Make the compiler much faster (hardly possible) or provide some way to
-make an image that includes everything loaded by startup.fs
 **Gender-independent image file format and loader
 **Stack Checking using the MMU where the OS makes it possible.
 
@@ -44,10 +41,11 @@ Use gcc-generated assembly on machines w
 processors supported by gcc
 
 *Foreign Language Interface
-If anybody wants to do this, mail me
-(anton@mips.complang.tuwien.ac.at). I have given some thought to this
-and will type in my notes if you are interested.
+If anybody wants to do this, take a look at
+ftp://ftp.complang.tuwien.ac.at/pub/forth/foreign.ds
+Some of the problems are discussed there,
 **C
+Stuart Ramsden is doing a bit here.
 **FORTRAN
 **C++
 
@@ -60,32 +58,31 @@ Issues: Convenience, portability across
 existing tools (Emacs, F-PC)
 ** Decompiler and Debugger
 need debugging
-**readline
-Use the GNU readline package for convenient line editing
+** Profiling
+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
+intended).
 ** emacs support
 can be improved
 **prefix file generator
-A tool for generating a prefix file for a program that explains in
-what way the program conforms to ANSI (i.e., which wordsets are used)
-and contains Forth definitions for the simple non-ANSI words.
+extend or complement ans-report.fs to provide Forth definitions for
+the simple non-ANSI words.
 ** rightcase
 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.
+search order tricks etc. EVALUATE is a problem.
 
-*Object-Oriented Extensions
-John Hayes has a portable package
-
-*Documentation
+*Documentation (Neal Crook, nac@forth.org is working on this)
 A texinfo file
-
+add more about internals (c primitives, creation of engine, etc.)
 **glossaries of all wordsets.
 *** Inclusion of stack comments, glossary comments, and wordset comments
 in all source files.
 
 * Distribution and Announcements
-** add copyright notices to all the source files
-** add a package target to the Makefile
 ** Write articles for (general-purpose) magazines