version 1.13, 1995/01/30 18:47:42
|
version 1.19, 1995/09/06 21:00:07
|
Line 1
|
Line 1
|
name> does not take the same argument as e.g. .name. Remedy: add cell+ |
|
before name>, but adapt all uses. anton 23apr94 Solved? |
|
|
|
revealing the same name several times (e.g., by using recursive) |
|
results in redefined messages. anton 28jul94 |
|
|
|
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 |
|
open-file, not create-file, read-file works. - anton 6aug94 |
|
|
|
etags.fs crashes one of my applications (gs.fs). anton 12jan95 |
etags.fs crashes one of my applications (gs.fs). anton 12jan95 |
|
|
f. suppresses all digits when it prints 0: |
|
0e0 f. . ok |
|
There's also one other problem with f.: |
|
1e-20 f. 0.00000000000000000001000000000000001 ok |
|
-20e0 falog f. 0.00000000000000000001000000000000001 ok |
|
0.00000000000000000001e0 f. 0.00000000000000000001000000000000001 ok |
|
All this happens under Slackware Linux. On the DecStation I get a |
|
similar error in the other direction. anton 17jan95 |
|
|
|
not all aliases are in the etags file. Bug in etags.fs? anton 24jan95 |
not all aliases are in the etags file. Bug in etags.fs? anton 24jan95 |
|
-> wrote special tag generation for cross compilation. bernd 6sep95 |
|
|
emacs often finds the wrong tag. anton 24jan95 |
emacs often finds the wrong tag. anton 24jan95 |
|
-> emacs does not search for a complete word, but for parts. |
|
-> Solution: add blanks in front and end of tag name (etags.fs) |
|
-> and use own forth-find-tag. bernd 6sep95 |
|
|
gforth.el: indentation does not work right on the first line of a |
gforth.el: indentation does not work right on the first line of a |
buffer. anton 27jan95 |
buffer. anton 27jan95 |
|
-> Solved? |
|
|
Conditional compilation continues after the file ends. This is allowed |
Conditional compilation continues after the file ends. This is allowed |
by the standard (through an ambiguous condition), but the compiler |
by the standard (through an ambiguous condition), but the compiler |
should at least produce a warning. anton 27jan95 |
should at least produce a warning. anton 27jan95 |
|
|
|
.1 is interpreted as floating-point number, not as double number or |
|
error. anton 4may95 |
|
-> All numbers ecvt converts are (by implementation) floating-point. |
|
-> Should we add a check againgst . at the start of a number? |
|
-> .1 isn't a double number; it's either an error or a FP number. |
|
-> bernd 5sep95 |
|
|
|
DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py |
|
|