version 1.7, 1994/08/31 16:37:44
|
version 1.22, 1996/08/26 10:07:17
|
Line 1
|
Line 1
|
name> does not take the same argument as e.g. .name. Remedy: add cell+ |
etags.fs crashes one of my applications (gs.fs). anton 12jan95 |
before name>, but adapt all uses. anton 23apr94 |
|
|
|
revealing the same name several times (e.g., by using recursive) |
gforth.el: indentation does not work right on the first line of a |
results in redefined messages. anton 28jul94 |
buffer. anton 27jan95 |
|
|
[IF] is case-sensitive. anton 2aug94 |
Conditional compilation continues after the file ends. This is allowed |
|
by the standard (through an ambiguous condition), but the compiler |
if blocks.fb does not exist, 1 block creates the file, but cannot |
should at least produce a warning. anton 27jan95 |
read-file from it. Only if the file-id has been created with |
|
open-file, not create-file, read-file works. - anton 6aug94 |
DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py |
|
|
gforth.el: doing a forth-fill-paragraph on the following piece of code |
see does not leave a space after two-digit literals: |
uncomments the first comment line. This may be a bug in |
: xxx 50 ; |
fill-paragraph, but documentation says that a paragraph can start |
see xxx |
without prefix (hanging indentation), so I guess it's all right. - |
gives |
anton 19aug94 |
: xxx |
|
50; |
: bb-shortest-paths recursive { bb bb-from start-path -- } |
|
\ compute the |
|
\ paths from bb-from through bb, start-path is the path from |
|
\ bb-from to bb |
|
|
|
|
|
etags.fs: The TAGS file for the kernal is strange: there are no tahs |
|
for some aliases; many constants and variables appear twice. |
|