| 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 |
| |
should at least produce a warning. anton 27jan95 |
| |
|
| if blocks.fb does not exist, 1 block creates the file, but cannot |
DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py |
| 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 |
see does not leave a space after two-digit literals: |
| |
: xxx 50 ; |
| |
see xxx |
| |
gives |
| |
: xxx |
| |
50; |
| |
|
| |
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 |
| |
|
| f. suppresses all digits when it prints 0: |
open-path-file expands "./" into the sourcefilename. It should either |
| 0e0 f. . ok |
not expand "./" or provide a mechanism that allows the application to |
| There's also one other problem with f.: |
determine what "./" should expand to. anton 16jun98 |
| 1e-20 f. 0.00000000000000000001000000000000001 ok |
|
| -20e0 falog f. 0.00000000000000000001000000000000001 ok |
|
| 0.00000000000000000001e0 f. 0.00000000000000000001000000000000001 ok |
|
| All this happens under Slackware Linux. Maybe the ecvt in the library |
|
| is not so good? anton 17jan95 |
|
