[gforth] / gforth / ToDo  

gforth: gforth/ToDo

Diff for /gforth/ToDo between version 1.3 and 1.4

version 1.3, Thu Feb 2 18:12:58 1995 UTC version 1.4, Thu Feb 9 17:49:53 1995 UTC
Line 13 
Line 13 
 **make it easy to put the right variation for each processor into the  **make it easy to put the right variation for each processor into the
 configuration. I.e., on installation all combinations of options  configuration. I.e., on installation all combinations of options
 should be measured and the fastest chosen. Knowing OS and architecture  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.  compiler version.
   
 * ANSI Forth  * ANSI Forth
Line 37 
Line 37 
 processors supported by gcc  processors supported by gcc
   
 *Foreign Language Interface  *Foreign Language Interface
 If anybody wants to do this, mail me  If anybody wants to do this, take a look at
 (anton@mips.complang.tuwien.ac.at). I have given some thought to this  ftp://ftp.complang.tuwien.ac.at/pub/forth/foreign.ds
 and will type in my notes if you are interested.  Some of the problems are discussed there,
 **C  **C
   Stuart Ramsden is doing a bit here.
 **FORTRAN  **FORTRAN
 **C++  **C++
   
Line 53 
Line 54 
 existing tools (Emacs, F-PC)  existing tools (Emacs, F-PC)
 ** Decompiler and Debugger  ** Decompiler and Debugger
 need debugging  need debugging
   ** 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  ** emacs support
 can be improved  can be improved
 **prefix file generator  **prefix file generator
Line 71 
Line 79 
   
 *Documentation  *Documentation
 A texinfo file  A texinfo file
   ** a tool that extracts (stack) comments from forth sources and replaces
   them in .ds files.
 **glossaries of all wordsets.  **glossaries of all wordsets.
 *** Inclusion of stack comments, glossary comments, and wordset comments  *** Inclusion of stack comments, glossary comments, and wordset comments
 in all source files.  in all source files.

Generate output suitable for use with a patch program
Legend:
Removed from v.1.3  
changed lines
  Added in v.1.4
CVS Admin

Powered by ViewCVS 1.0-dev 		(Powered by ViewCVS)

ViewCVS and CVS Help