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

Diff for /gforth/BUGS between versions 1.8 and 1.24

version 1.8, 1994/09/05 17:36:15 version 1.24, 1998/06/17 16:55:04
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
 if blocks.fb does not exist, 1 block creates the file, but cannot  should at least produce a warning.  anton 27jan95
 read-file from it. Only if the file-id has been created with  
 open-file, not create-file, read-file works. - anton 6aug94  DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py
   
 gforth.el: doing a forth-fill-paragraph on the following piece of code  see does not leave a space after two-digit literals:
 uncomments the first comment line. This may be a bug in    : xxx 50 ;
 fill-paragraph, but documentation says that a paragraph can start    see xxx
 without prefix (hanging indentation), so I guess it's all right. -  gives
 anton 19aug94    : xxx  
     50;
 : bb-shortest-paths recursive { bb bb-from start-path -- }  
     \ compute the  QUERY and TIB may behave differently than some may expect. TIB always
     \ paths from bb-from through bb, start-path is the path from  points to the current SOURCE, and QUERY puts its result there.  anton
     \ bb-from to bb  28nov96
   
   open-path-file expands "./" into the sourcefilename. It should either
 etags.fs: The TAGS file for the kernal is strange: there are no tags  not expand "./" or provide a mechanism that allows the application to
 for some aliases; many constants and variables appear twice. anton  determine what "./" should expand to. anton 16jun98
 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.24

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