version 1.11, 1995/01/18 18:41:30
|
version 1.44, 2000/09/14 19:16:23
|
Line 1
|
Line 1
|
name> does not take the same argument as e.g. .name. Remedy: add cell+ |
gforth.el: indentation does not work right on the first line of a |
before name>, but adapt all uses. anton 23apr94 |
buffer. anton 27jan95 |
|
|
revealing the same name several times (e.g., by using recursive) |
Conditional compilation continues after the file ends. This is allowed |
results in redefined messages. anton 28jul94 |
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 |
open-path-file expands "./" into the sourcefilename. It should either |
read-file from it. Only if the file-id has been created with |
not expand "./" or provide a mechanism that allows the application to |
open-file, not create-file, read-file works. - anton 6aug94 |
determine what "./" should expand to. anton 16jun98 |
|
|
etags.fs crashes one of my applications (gs.fs). anton 12jan95 |
gforth.el: Typing <ret> does not work when tabs separate words in a |
|
line, and there is a \-comment at the end of the line. anton 19feb00 |
f. suppresses all digits when it prints 0: |
|
0e0 f. . ok |
SEE does not work when the control structure is too complex (e.g., |
There's also one other problem with f.: |
load http://www.complang.tuwien.ac.at/forth/pentomino.fs and then do |
1e-20 f. 0.00000000000000000001000000000000001 ok |
SEE NEXT-PIECE). anton 5mar2000 |
-20e0 falog f. 0.00000000000000000001000000000000001 ok |
|
0.00000000000000000001e0 f. 0.00000000000000000001000000000000001 ok |
RESTORE-INPUT does not work for files with CRLF newlines, and if |
All this happens under Slackware Linux. Maybe the ecvt in the library |
SAVE-INPUT was called on a line without newline (i.e., on the last |
is not so good? anton 17jan95 |
line) anton 27apr2000 |
|
|
|
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 |