Diff for /gforth/BUGS between versions 1.2 and 1.13

version 1.2, 1994/05/07 14:55:44 version 1.13, 1995/01/30 18:47:42
Line 1 Line 1
 The system quits on exceptions like segmentation faults. anton 5oct93  name> does not take the same argument as e.g. .name. Remedy: add cell+
   before name>, but adapt all uses.  anton 23apr94 Solved?
 compile does not have its traditional meaning. anton 5oct93  
   
 include does not read the last line if it does not end with \n.  anton 6oct93  
   
 in decimal mode aaa is accepted as 1110  anton 4feb94  revealing the same name several times (e.g., by using recursive)
   results in redefined messages.  anton 28jul94
   
 abort" does something to the control flow stack  anton 2mar94  if blocks.fb does not exist, 1 block creates the file, but cannot
   read-file from it. Only if the file-id has been created with
   open-file, not create-file, read-file works. - anton 6aug94
   
 the compiler does not complain about undefined words; instead, it  etags.fs crashes one of my applications (gs.fs). anton 12jan95
 complains about unstructured  anton 2mar94  
   
 the compiler tries to reveal anonymous words ( -> redefined complaints )  anton 2mar94  f. suppresses all digits when it prints 0:
   0e0 f. .  ok
   There's also one other problem with f.:
   1e-20                    f. 0.00000000000000000001000000000000001  ok
   -20e0 falog              f. 0.00000000000000000001000000000000001  ok
   0.00000000000000000001e0 f. 0.00000000000000000001000000000000001  ok
   All this happens under Slackware Linux. On the DecStation I get a
   similar error in the other direction.  anton 17jan95
   
 'ansforth "include xxx"' gives a segmentation fault after processing  not all aliases are in the etags file. Bug in etags.fs? anton 24jan95
 the file; No segmentation fault when including from the Forth prompt  
 anton 2apr94  
   
 name> does not take the same argument as e.g. .name. Remedy: add cell+  emacs often finds the wrong tag. anton 24jan95
 before name>, but adapt all uses.  anton 23apr94  
   
   gforth.el: indentation does not work right on the first line of a
   buffer. anton 27jan95
   
   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

Removed from v.1.2  
changed lines
  Added in v.1.13


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