Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tellab5!vpnet!dattier
From: dattier@vpnet.chi.il.us (David W. Tamkin)
Newsgroups: comp.sys.cbm
Subject: Re: Reading SEQ files
Message-ID: <1991Mar03.040605.29288@vpnet.chi.il.us>
Date: 3 Mar 91 04:06:05 GMT
References: <1991Feb27.213545.18354@nntp-server.caltech.edu> <1991Mar02.032753.23899@ddsw1.MCS.COM> <1991Mar2.115333.11011@evax.arl.utexas.edu>
Organization: VPnet Public Access Unix, Villa Park, Illinois  60181-2206
Lines: 28

cs4344af@evax.arl.utexas.edu (David "Fuzzy Fox" DeSimone) wrote in
<1991Mar2.115333.11011@evax.arl.utexas.edu>:

| In article <1991Mar02.032753.23899@ddsw1.MCS.COM> dattier@ddsw1.MCS.COM
| (David W. Tamkin) writes:

| >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.

Fuzzy Fox's 64 and mine must have different OS's in ROM then, or at least
different BASIC interpreters.

In order to use the FOR-NEXT loop instead of gotos (and speed the routine
up), one needs x=st somewhere in there, and even if printing to the screen
doesn't affect st and you can set x=st after the PRINT, it doesn't hurt to
do it between the GET# and the PRINT.  Of course, if you are printing a disk
file to the printer, my original caution stands uncontested.  

David Tamkin  PO Box 7002  Des Plaines IL  60018-7002  dattier@vpnet.chi.il.us
GEnie:D.W.TAMKIN  CIS:73720,1570  MCIMail:426-1818  708 518 6769  312 693 0591

"Parker Lewis Can't Lose" mailing list:   write flamingo-request@ddsw1.mcs.com