Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!evax!cs4344af
From: cs4344af@evax.arl.utexas.edu (Fuzzy Fox)
Newsgroups: comp.sys.cbm
Subject: Re: Reading SEQ files
Message-ID: <1991Mar2.115333.11011@evax.arl.utexas.edu>
Date: 2 Mar 91 11:53:33 GMT
References: <13324@hubcap.clemson.edu> <1991Feb27.213545.18354@nntp-server.caltech.edu> <1991Mar02.032753.23899@ddsw1.MCS.COM>
Organization: Computer Science Engineering Univ. of Texas at Arlington
Lines: 17

In article <1991Mar02.032753.23899@ddsw1.MCS.COM> dattier@ddsw1.MCS.COM (David W. Tamkin) writes:
>| 30 get#1,a$:printa$;
>
>That won't work; the print statement (to the screen) in line 30 will re-zero
>st and the loop will not break when the end of the disk file is reached.

I can't let this go by...The print statement will NOT change the ST
variable at all.  Only statements that perform serial or RS-232 I/O will
affect ST, meaning only PRINT# or GET# statements.  (Well, a POKE to 144
would have an effect...)  Anyway, PRINT or GET statements from screen or
keyboard do not affect ST.

-- 
David DeSimone, aka "Fuzzy Fox" on some networks.          /!/!
INET:    an207@cleveland.freenet.edu                      /  ..
Q-Link:  Fuzzy Fox                                        /   --*
Quote:   "Foxes are people too!  And vice versa."         /  ---