zippy - yet another serial fastloader

[srowe]

It's in line to your proposal, but please check my preceding post why it could be a good idea to simply keep the BCC loop instead.

I think our posts crossed, if you abort the close the new behaviour still completely clears the file table. You don't get a second chance.

[Mike]

I think our posts crossed, [...]

That's why I asked you to take my post one further up into consideration.

[...] if you abort the close the new behaviour still completely clears the file table. You don't get a second chance.

With your implementation, yes. It's an equally valid approach to handle the situation, yet still needs to be documented (TBH - seeing that prompt to press record upon CLR/RUN/edit has a good potential to surprise people).

[srowe]

[...] if you abort the close the new behaviour still completely clears the file table. You don't get a second chance.

With your implementation, yes. It's an equally valid approach to handle the situation, yet still needs to be documented (TBH - seeing that prompt to press record upon CLR/RUN/edit has a good potential to surprise people).

OK, I've gone with your suggestion and terminate the loop if there's an error, it keeps the code simple. I would expect the new option to be used within an application rather than with BASIC, otherwise the change in behaviour is going to cause confusion as you note.