version 1.8, 1994/09/05 17:36:15
|
version 1.11, 1995/01/18 18:41:30
|
Line 10 if blocks.fb does not exist, 1 block cre
|
Line 10 if blocks.fb does not exist, 1 block cre
|
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 |
|
without prefix (hanging indentation), so I guess it's all right. - |
|
anton 19aug94 |
|
|
|
: bb-shortest-paths recursive { bb bb-from start-path -- } |
f. suppresses all digits when it prints 0: |
\ compute the |
0e0 f. . ok |
\ paths from bb-from through bb, start-path is the path from |
There's also one other problem with f.: |
\ bb-from to bb |
1e-20 f. 0.00000000000000000001000000000000001 ok |
|
-20e0 falog f. 0.00000000000000000001000000000000001 ok |
|
0.00000000000000000001e0 f. 0.00000000000000000001000000000000001 ok |
etags.fs: The TAGS file for the kernal is strange: there are no tags |
All this happens under Slackware Linux. Maybe the ecvt in the library |
for some aliases; many constants and variables appear twice. anton |
is not so good? anton 17jan95 |
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 |
|