version 1.8, 1994/09/05 17:36:15
|
version 1.45, 2000/09/23 12:27:45
|
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 |
|
|
gforth.el: doing a forth-fill-paragraph on the following piece of code |
gforth.el: Typing <ret> does not work when tabs separate words in a |
uncomments the first comment line. This may be a bug in |
line, and there is a \-comment at the end of the line. anton 19feb00 |
fill-paragraph, but documentation says that a paragraph can start |
|
without prefix (hanging indentation), so I guess it's all right. - |
SEE does not work when the control structure is too complex (e.g., |
anton 19aug94 |
load http://www.complang.tuwien.ac.at/forth/pentomino.fs and then do |
|
SEE NEXT-PIECE). anton 5mar2000 |
: bb-shortest-paths recursive { bb bb-from start-path -- } |
|
\ compute the |
Include cannot handle lines longer than 255 characters. anton 4sep00 |
\ paths from bb-from through bb, start-path is the path from |
|
\ bb-from to bb |
Errors happening during a LOAD do not report the offending word and |
|
its context (e.g., the 64-byte line). anton 8sep00 |
|
|
etags.fs: The TAGS file for the kernal is strange: there are no tags |
|
for some aliases; many constants and variables appear twice. anton |
|
2sep94 |
|
|
|
error-causing word indication no longer works well. Cause: relies on |
|
name being HERE. Future trouble (once CATCH really restores the input |
|
stream): it also relies on SOURCE delivering the line that caused the |
|
error. anton 2sep94 |
|