BIN work as you would
W/O translates into the C file opening mode
wb): The file is cleared, if it exists, and created, if it does
not (with both
create-file). Under Unix
create-file creates a file with 666 permissions modified by your
The file words do not raise exceptions (except, perhaps, memory access faults when you pass illegal addresses or file-ids).
System-dependent. Gforth uses C’s newline character as line terminator. What the actual character code(s) of this are is system-dependent.
System dependent. Gforth just uses the file name format of your OS.
FILE-STATUS returns the most powerful file access mode allowed
for the file: Either
R/W. If the file
cannot be accessed,
R/O BIN is returned.
BIN is applicable
along with the returned mode.
All files that are left via the exception are closed.
The iors returned by the file and memory allocation words are intended as throw codes. They typically are in the range -512--2047 of OS errors. The mapping from OS error numbers to iors is -512-errno.
limited by the amount of return stack, locals/TIB stack, and the number of open files available. This should not give you troubles.
/line. Currently 255.
By default, blocks are accessed in the file blocks.fb in the
current working directory. The file can be switched with
As many as memory available; the strings are stored in memory blocks allocated with ALLOCATE indefinitely.
/line. currently 255.