[BACK]Return to BUGS CVS log [TXT] [DIR] Up to [gforth] / gforth

Diff for /gforth/BUGS between versions 1.8 and 1.20

version 1.8, 1994/09/05 17:36:15 version 1.20, 1995/10/07 17:42:14
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)  not all aliases are in the etags file. Bug in etags.fs? anton 24jan95
 results in redefined messages.  anton 28jul94  -> wrote special tag generation for cross compilation. bernd 6sep95
   
 [IF] is case-sensitive.  anton 2aug94  emacs often finds the wrong tag. anton 24jan95
   -> emacs does not search for a complete word, but for parts.
   -> Solution: add blanks in front and end of tag name (etags.fs)
   -> and use own forth-find-tag. bernd 6sep95
   
 if blocks.fb does not exist, 1 block creates the file, but cannot  gforth.el: indentation does not work right on the first line of a
 read-file from it. Only if the file-id has been created with  buffer. anton 27jan95
 open-file, not create-file, read-file works. - anton 6aug94  -> Solved?
   
 gforth.el: doing a forth-fill-paragraph on the following piece of code  Conditional compilation continues after the file ends. This is allowed
 uncomments the first comment line. This may be a bug in  by the standard (through an ambiguous condition), but the compiler
 fill-paragraph, but documentation says that a paragraph can start  should at least produce a warning.  anton 27jan95
 without prefix (hanging indentation), so I guess it's all right. -  
 anton 19aug94  
   
 : bb-shortest-paths recursive { bb bb-from start-path -- }  DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py
     \ 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 tags  
 for some aliases; many constants and variables appear twice. anton  
 2sep94  
   
 error-causing word indication no longer works well. Cause: relies on  
 name being HERE. Future trouble (once CATCH really restores the input  
 stream): it also relies on SOURCE delivering the line that caused the  
 error. anton 2sep94  
   
Removed from v.1.8  
changed lines
  Added in v.1.20

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