Re: Whatever happened to...

[vandry@CAM.ORG (Phillip Vandry)]

mark@pokey.jsc.nasa.gov (Mark Manning) writes:

>First, thanks to everyone who has sent me suggestions and help as well as
>everyone who has posted something. There were a lot of ideas on what might
>be wrong and (although I just got to work and read everything) I think I
>might have found out what is wrong (I'll be trying it tonight).

>What I believe might be the problem is in how I am opening the files.
>Under DOS 3.3 I would open and allocate the function to the file before
>continuing on with the rest of the program.  It looks like under ProDOS
>that you have to open all of the files *first* and then allocate their
>functions.

OPEN and CLOSE commands do indeed disable all READ and WRITE commands. Of couse
a READ disables a previous read or IN# and a IN# disables a previous READ or
IN#. Same for write and PR#.

A good idea if your program is getting confused and there are more than one file
open is to issue a READ file or IN#0 (for input from keyboard without closing
any files) before INPOUTS and GETS and to issue a WRITE or PR#0 (output to
screen) before PRINTs. he overhead for those statemnts is minimal and it
helps the program's readability a lot. Just a suggestioin.

 ______________________________________________________________________
|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~~~~|
| Phillip Vandry | Vandry@Cam.Org | II the future! | II 1993!          |
|________________|________________|________________|___________________|
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~