1: etags.fs crashes one of my applications (gs.fs). anton 12jan95
2:
3: gforth.el: indentation does not work right on the first line of a
4: buffer. anton 27jan95
5:
6: Conditional compilation continues after the file ends. This is allowed
7: by the standard (through an ambiguous condition), but the compiler
8: should at least produce a warning. anton 27jan95
9:
10: QUERY and TIB may behave differently than some may expect. TIB always
11: points to the current SOURCE, and QUERY puts its result there. anton
12: 28nov96
13:
14: open-path-file expands "./" into the sourcefilename. It should either
15: not expand "./" or provide a mechanism that allows the application to
16: determine what "./" should expand to. anton 16jun98
17:
18: TAGS contains references to development (not install, not build)
19: directories (for prim). Probably a Makefile bug. anton 20oct99
20:
21: All I/O in DOS is unbuffered since 0.4.0. Bruce Hoyt, early 1999.
22:
23: FILE-SIZE, FILE-POSITION, and REPOSITION-FILE don't work correctly on
24: text files under DOS and Windows. anton 31oct99
25:
26: On Irix 6.2 the second signal kills gforth. anton 31oct99
27:
28: gforth.el: Typing <ret> does not work when tabs separate words in a
29: line, and there is a \-comment at the end of the line. anton 19feb00
30:
31: If I start Gforth and type first
32: : 123456789012345678901234567890 ;
33: ' 123456789012345678901234567890 >name name>string type gives ??? ok
34: Robert Epprecht 18mar00
35:
36: EKEY no longer works (does not recognize function keys etc.). anton 23feb2000
37:
38: SEE does not work when the control structure is too complex (e.g.,
39: load http://www.complang.tuwien.ac.at/forth/pentomino.fs and then do
40: SEE NEXT-PIECE). anton 5mar2000
41:
42: RESTORE-INPUT does not work for files with CRLF newlines, and if
43: SAVE-INPUT was called on a line without newline (i.e., on the last
44: line) anton 27apr2000
45:
46: The output of .included for gforth.fi does not include exboot.fs and
47: exceptions.fs anton 1jul00
48:
49: When arch/alpha/asm.fs is somewhere on the path (not in the wd), and
50: includes ../../code.fs, Gforth should interpret .. relative to the
51: position of asm.fs, but doesn't. anton 15jul00
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>