--- gforth/BUGS 1995/01/18 18:41:30 1.11 +++ gforth/BUGS 2000/09/23 12:27:45 1.45 @@ -1,22 +1,26 @@ -name> does not take the same argument as e.g. .name. Remedy: add cell+ -before name>, but adapt all uses. anton 23apr94 +gforth.el: indentation does not work right on the first line of a +buffer. anton 27jan95 -revealing the same name several times (e.g., by using recursive) -results in redefined messages. anton 28jul94 +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 -[IF] is case-sensitive. anton 2aug94 +QUERY and TIB may behave differently than some may expect. TIB always +points to the current SOURCE, and QUERY puts its result there. anton +28nov96 -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 - -etags.fs crashes one of my applications (gs.fs). anton 12jan95 - -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. Maybe the ecvt in the library -is not so good? anton 17jan95 +open-path-file expands "./" into the sourcefilename. It should either +not expand "./" or provide a mechanism that allows the application to +determine what "./" should expand to. anton 16jun98 + +gforth.el: Typing does not work when tabs separate words in a +line, and there is a \-comment at the end of the line. anton 19feb00 + +SEE does not work when the control structure is too complex (e.g., +load http://www.complang.tuwien.ac.at/forth/pentomino.fs and then do +SEE NEXT-PIECE). anton 5mar2000 + +Include cannot handle lines longer than 255 characters. anton 4sep00 + +Errors happening during a LOAD do not report the offending word and +its context (e.g., the 64-byte line). anton 8sep00