Re: Integer BASIC's "*** NO END ERR"

[Don Bruder <dakidd@sonic.net>]

In article <d9k9j5$i6h$1@ottoman.cs.fiu.edu>,
 Zorin the Lynx <yakko@zorin.org> wrote:

> Ya know, I've always wondered why an END statement was required in 
> Integer BASIC programs on the Apple II. And if you didn't put one in, 
> you got the "NO END ERR" message.
> 
> Why not just exit quietly when the program finished? The "NO END ERR" 
> message wasted valuable ROM space, and had no useful function.
> 
> Anyone have any insight as to why Woz put this seemingly useless error 
> into INTBASIC? Did he just have extra space and wanted to fill it with 
> something?
> 
> -Z

Seems to me that Integer was (comparatively) brain-dead when it came to 
figuring out where program code left off and variable storage began.

-- 
Don Bruder - dakidd@sonic.net - New Email policy in effect as of Feb. 21, 2004.
Short form: I'm trashing EVERY E-mail that doesn't contain a password in the
subject unless it comes from a "whitelisted" (pre-approved by me) address.
See <http://www.sonic.net/~dakidd/main/contact.html> for full details.