What about handling strange situations and errors?
How is a file of unknown size (e.g. serial port) read til end-of-file? Until an error occurs?
How are errors handled? Reading past end-of-input-file, seeking past end-of-input-file, writing to write protected file, writing to full stick?
The software should be able to handle this situations: no hard return to BASIC throwing a "standard error" and interrupting everything...
Siggi
Balancing compatibility with innovation .. ZXPand(+)
Re: Balancing compatibility with innovation .. ZXPand(+)
My ZX81 web-server: online since 2007, running since dec. 2020 using ZeddyNet hardware
http://zx81.ddns.net/ZxTeaM
http://zx81.ddns.net/ZxTeaM
Re: Balancing compatibility with innovation .. ZXPand(+)
Every request should be answered with a data block. If a header is provided for each data block, any errors can be written too. And of course the length of the data block should be provided which can be quite small when an error occurred. I think this would be more or less standard for any software interface.