Re: How to detect EOFs in SEQ-files using M/C?

[pausch@saaf.se (Paul Schlyter)]

In article <3d7d22c4$1_2@news2.newsgroups.com>,
Scott Alfter <salfter@salfter.dyndns.org> wrote:
 
>> From what I can vaguely recall, there was more than one kind of
>> Applesoft Basic out there.  I think there was something called
>> 'integer basic' that performed very well compared to floating point.
> 
> Integer BASIC != Applesoft.  The former was limited to 16-bit integer math,
> while the latter does single-precision floating point.  Applesoft also
> allows character arrays; Integer BASIC doesn't.  OTOH, Integer BASIC was
> supposed to be somewhat faster at some things...I guess that says something
> about Steve Wozniak's coding skillz vs. Bill Gates' coding skillz. :-)
 
Integer Basic used a much more complex tokenization of the Basic
source (integer constants for instance were stored in binary form; a
comma could be one of several different tokens depending on where it
appeared, etc etc) while Applesoft used a very simple-minded
approach: reserved words were tokenized, spaces were removed except
in string constants, and everything else were left as plain ASCII.
This meant that in e.g.:
 
    FOR I=100 TO 1000 STEP 10
 
Integer Basic stored the "10", "1000" and "100" in binary form, while
Applesoft left then in ASCII form.  Which meant that Applesoft had to
convert the ASCII string of digits to binary for each and every loop!
And Applesoft converted then to floating-point too!  Since Applesoft
had no way to distinguish an integer constant from a floating-point
constant....
 
 
-- 
----------------------------------------------------------------
Paul Schlyter,  Swedish Amateur Astronomer's Society (SAAF)
Grev Turegatan 40,  S-114 38 Stockholm,  SWEDEN
e-mail:  pausch at saaf dot se
WWW:     http://hem.passagen.se/pausch/index.html
         http://home.tiscali.se/~pausch/