I have used both systems, and I agree with you. The way Computer One Forth handles block is better. That's the way most Forth systems do it, when simulating blocks on ordinary files.polka wrote: The way blocks are managed in the two FORTH machines that I know are running on the QL (the Computer One FORTH and the Digital Precision SuperFORTH) are completely opposed and I prefer the Computer One way :
Are you sure the source of Reversi was included with SuperForth? It was listed on the manual, but I think only the binary was included on the disk. I have to check my DP Collection. I think Reversi was included on a different disk.polka wrote: SuperFORTH obviously prefers text source files (as all the added packages like the editor ... the reversi) are provided in this form.
Yes, it should not be difficult to implement text source files on Computer One Forth, and also to improve the way SuperForth handles them (for example, make then nestable).polka wrote: So I would advise not to bother any longer with block files managers (especially the Digital Precision ones) and to adopt preferably text source files. They are not supported by Computer One FORTH, but I feel their management should be rather easy to implement and I will do it.
If you develop for Computer One Forth or SuperForth, on a computer you can install Vim or Gforth on, you may find useful the converters I wrote:
I find them very useful. They allow you to edit Forth sources with almost all the advantages of source text files, and almost no disadvantage of blocks, and convert them to blocks suitable for different Forth systems (the standard target format .fb is suitable for Computer One Forth, and a specific converter is included for SuperForth).
I invite you to join Forth on Sinclair (and Z80) computers email list. There are some QL users there.polka wrote: May the FORTH be with you !