| name> does not take the same argument as e.g. .name. Remedy: add cell+ |
name> does not take the same argument as e.g. .name. Remedy: add cell+ |
| before name>, but adapt all uses. anton 23apr94 |
before name>, but adapt all uses. anton 23apr94 Solved? |
| |
|
| revealing the same name several times (e.g., by using recursive) |
revealing the same name several times (e.g., by using recursive) |
| results in redefined messages. anton 28jul94 |
results in redefined messages. anton 28jul94 |
| |
|
| [IF] is case-sensitive. anton 2aug94 |
|
| |
|
| if blocks.fb does not exist, 1 block creates the file, but cannot |
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 |
read-file from it. Only if the file-id has been created with |
| open-file, not create-file, read-file works. - anton 6aug94 |
open-file, not create-file, read-file works. - anton 6aug94 |
| |
|
| gforth.el: doing a forth-fill-paragraph on the following piece of code |
etags.fs crashes one of my applications (gs.fs). anton 12jan95 |
| uncomments the first comment line. This may be a bug in |
|
| fill-paragraph, but documentation says that a paragraph can start |
f. suppresses all digits when it prints 0: |
| without prefix (hanging indentation), so I guess it's all right. - |
0e0 f. . ok |
| anton 19aug94 |
There's also one other problem with f.: |
| |
1e-20 f. 0.00000000000000000001000000000000001 ok |
| : bb-shortest-paths recursive { bb bb-from start-path -- } |
-20e0 falog f. 0.00000000000000000001000000000000001 ok |
| \ compute the |
0.00000000000000000001e0 f. 0.00000000000000000001000000000000001 ok |
| \ paths from bb-from through bb, start-path is the path from |
All this happens under Slackware Linux. On the DecStation I get a |
| \ bb-from to bb |
similar error in the other direction. anton 17jan95 |
| |
|
| |
not all aliases are in the etags file. Bug in etags.fs? anton 24jan95 |
| etags.fs: The TAGS file for the kernal is strange: there are no tags |
|
| for some aliases; many constants and variables appear twice. anton |
emacs often finds the wrong tag. anton 24jan95 |
| 2sep94 |
|
| |
gforth.el: indentation does not work right on the first line of a |
| error-causing word indication no longer works well. Cause: relies on |
buffer. anton 27jan95 |
| name being HERE. Future trouble (once CATCH really restores the input |
|
| stream): it also relies on SOURCE delivering the line that caused the |
Conditional compilation continues after the file ends. This is allowed |
| error. anton 2sep94 |
by the standard (through an ambiguous condition), but the compiler |
| |
should at least produce a warning. anton 27jan95 |
