Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!cbmvax!grr
From: grr@cbmvax.cbm.UUCP (George Robbins)
Newsgroups: net.micro.atari16
Subject: Re: Atari Basic
Message-ID: <406@cbmvax.cbmvax.cbm.UUCP>
Date: Sun, 15-Jun-86 03:06:55 EDT
Article-I.D.: cbmvax.406
Posted: Sun Jun 15 03:06:55 1986
Date-Received: Tue, 17-Jun-86 22:37:17 EDT
References: <631@marlin.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 22

In article <631@marlin.UUCP> dobbs@cod.UUCP (Lynn B. Dobbs) writes:
>
>I recently pulled a basic program from "sources," and tried to 
>adapt it for Atari Basic (Yech).  It bombs out with a "Too many 
>FOR loops" error.  What does it mean?
>
>Does Atari basic look for certain types of errors before it 
>begins program execution?  The first program line contained 
>"FULLW 2" and CLEARW 2," but neither happened.  Just the error.
>

Many basic interpreters do a quick scan when you type run, to tie
together for/next loops, def fn - call, and data statements.

As to your particular error, it could mean you have to many for
loops, loops nested too deep, or problems with matching the control
variable on the for/next pair - some require a variable and some
don't.
-- 
George Robbins - now working with,	uucp: {ihnp4|seismo|caip}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@seismo.css.GOV
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)