Return to BUGS CVS log

Up to [gforth] / gforth

Annotation of gforth/BUGS, revision 1.13

1.2       anton       1: name> does not take the same argument as e.g. .name. Remedy: add cell+
1.13    ! anton       2: before name>, but adapt all uses.  anton 23apr94 Solved?
1.2       anton       3: 
1.6       anton       4: revealing the same name several times (e.g., by using recursive)
1.4       anton       5: results in redefined messages.  anton 28jul94
1.1       anton       6: 
1.5       anton       7: if blocks.fb does not exist, 1 block creates the file, but cannot
                      8: read-file from it. Only if the file-id has been created with
                      9: open-file, not create-file, read-file works. - anton 6aug94
1.6       anton      10: 
1.11      anton      11: etags.fs crashes one of my applications (gs.fs). anton 12jan95
                     12: 
                     13: f. suppresses all digits when it prints 0:
                     14: 0e0 f. .  ok
                     15: There's also one other problem with f.:
                     16: 1e-20                   f. 0.00000000000000000001000000000000001  ok
                     17: -20e0 falog             f. 0.00000000000000000001000000000000001  ok
                     18: 0.00000000000000000001e0 f. 0.00000000000000000001000000000000001  ok
1.12      anton      19: All this happens under Slackware Linux. On the DecStation I get a
                     20: similar error in the other direction.  anton 17jan95
                     21: 
                     22: not all aliases are in the etags file. Bug in etags.fs? anton 24jan95
                     23: 
                     24: emacs often finds the wrong tag. anton 24jan95
                     25: 
1.13    ! anton      26: gforth.el: indentation does not work right on the first line of a
        !            27: buffer. anton 27jan95
        !            28: 
        !            29: Conditional compilation continues after the file ends. This is allowed
        !            30: by the standard (through an ambiguous condition), but the compiler
        !            31: should at least produce a warning.  anton 27jan95