Seems like files should be closed, just like clearing all the other variables, when RUN is executed. I can’t remember exactly how the TRS-80 and gwBASIC handled things because I can’t remember ever running into a time where files were accidentally left open when RUNing another program. This is really odd behavior. The only time files should be left open when starting a new program is through the CHAIN command.
Seems like files **should** be closed, just like clearing all the other variables, when `RUN` is executed. I can't remember exactly how the TRS-80 and gwBASIC handled things because I can't remember ever running into a time where files were accidentally left open when RUNing another program. This is really odd behavior. The only time files should be left open when starting a new program is through the `CHAIN` command.
Seems like files should be closed, just like clearing all the other variables, when
RUN
is executed. I can’t remember exactly how the TRS-80 and gwBASIC handled things because I can’t remember ever running into a time where files were accidentally left open when RUNing another program. This is really odd behavior. The only time files should be left open when starting a new program is through theCHAIN
command.I noticed variables get dumped upon
LOAD
andNEW
. The files auto-closing should follow the same rules as variable dumping.Confirmed with
BASICA
files are closed uponRUN
.Files left opento Files left open =-O 2 years agoFixed in commit
9ca2d013