-
Notifications
You must be signed in to change notification settings - Fork 1
06.Known bugs, workarounds, and improvement needed
The INCLUDEd source text file must end with an empty line, otherwise the system crashes usually showing some vertical grid. NEEDS suffers the same bug since it uses INCLUDE.
In case of interpretation/compilation error, the file-handle remains open and you have to manually close it using something like 2 F_CLOSE . and you cannot use REMOUNT until then. The same problem arises using other disk related definitions.
In some cases, interpretation of long structure via LOAD cannot cope with BLOCKs boundaries within the same Screen. This means, for example, that you cannot start an ENUMERATED structure in the first BLOCK of a Screen and continue it in the next one.
A 'nul' character (0x00) inside a Screen is completely invisible and is the source of most headache because it provokes an immediate stop loading. To remove such characters you have to edit the Screen.
At the moment, this definition can be used only in interpretation mode.
When used repeatedly, it seem to miss half Screen every three, expecially when you work backard in block number. Maybe this depends from the number of BUFFERs available. A simple workaround is to FLUSH often.
Pressing [BREAK] will stop any I/O operations: if not correctly used, may produce data-loss.
vForth-Next - a Sinclair ZX Spectrum Next Forth