Diff for /gforth/BUGS between versions 1.7 and 1.21

version 1.7, 1994/08/31 16:37:44 version 1.21, 1995/12/26 17:35:32
Line 1 Line 1
 name> does not take the same argument as e.g. .name. Remedy: add cell+  etags.fs crashes one of my applications (gs.fs). anton 12jan95
 before name>, but adapt all uses.  anton 23apr94  
   
 revealing the same name several times (e.g., by using recursive)  gforth.el: indentation does not work right on the first line of a
 results in redefined messages.  anton 28jul94  buffer. anton 27jan95
   
 [IF] is case-sensitive.  anton 2aug94  Conditional compilation continues after the file ends. This is allowed
   by the standard (through an ambiguous condition), but the compiler
   should at least produce a warning.  anton 27jan95
   
 if blocks.fb does not exist, 1 block creates the file, but cannot  DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py
 read-file from it. Only if the file-id has been created with  
 open-file, not create-file, read-file works. - anton 6aug94  
   
 gforth.el: doing a forth-fill-paragraph on the following piece of code  
 uncomments the first comment line. This may be a bug in  
 fill-paragraph, but documentation says that a paragraph can start  
 without prefix (hanging indentation), so I guess it's all right. -  
 anton 19aug94  
   
 : bb-shortest-paths recursive { bb bb-from start-path -- }  
     \ compute the  
     \ paths from bb-from through bb, start-path is the path from  
     \ bb-from to bb  
   
   
 etags.fs: The TAGS file for the kernal is strange: there are no tahs  
 for some aliases; many constants and variables appear twice.  
   

Removed from v.1.7  
changed lines
  Added in v.1.21


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>