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

[Matthew Montchalin <mmontcha@OregonVOS.net>]

On Mon, 9 Sep 2002, BlackJack wrote:
|On Mon, 09 Sep 2002 00:24:43 +0000, Matthew Montchalin wrote:
|
|> [BASIC tokens] The concept behind tokens is that you save space that
|> way.
|
|I think that's a nice side effect. The main reason for using tokens is
|execution speed of the interpreter which has just to take a look at *one*
|byte and can use a jump table to the routine that executes that particular
|BASIC command. Just imagine how slow a program becomes if the interpreter
|has to compare the commands as strings while executing.

Hmmm. How does Applesoft BASIC compare to Commodore BASIC, then?  I am
not trying to start a flame war, but weren't there some benchmark tests
once upon a time that COMPUTER SHOPPER used to use for deciding which
computer was faster than another?  And here, the thing I am wondering
about, is how Applesoft BASIC was put together, and why on earth Commdore
BASIC used a token to represent pi.  Are mathematical formulas involving
pi evaluated faster on the Commodore because of the pi token?