Brian...

"Learn the tools you use and profit from the advice of others."

For a year and a half, you've been asking for help on this with a 
multitude of people supplying answers and providing important 
programming techniques and sample code. Yet here you revert back to 
where you were long ago, committing the same mistake that many, many 
have cautioned you about.

	DEFINE YOUR VARIABLES!
	Use this preference to be sure:  "Use DIMensioned variables only."

It appears in your example that you didn't do that -- AGAIN -- and as a 
result, the variable "theRest" is treated as an integer rather than a 
string which is needed the way you want.

You appear to have make very little effort to improve your habits or 
knowledge of important programming concepts or to take the advice 
offered. I and others have provided many examples from a small 
beginning and slowly adding more, testing as we go, to show concepts 
like using arrays (for parts of an instruction or for variables) and a 
multitude of functions to produce a structured program that is a 
relatively simple interpreter.

My final bit of advice is to find a book or two on programming 
techniques and study them, trying all the examples and reading the 
explanations. Not just how to get started but all the details like the 
string functions, arrays, variable types, records, functions, 
parameters, recursion, and everything else. As with any trade or 
profession, one needs to understand a tool before using it wisely.

You may also want to review my series of e-mails last summer showing 
the early development of the BYH-BASIC interpreter so far from its 
inception. If you do, be sure to study the HELP files too re any 
instructions you are not sure of. Complex problems need complex 
solutions but they can be broken down into manageable steps with 
planning and efficient data structures.

( PS   For those following this thread, BYH stands for 'Bang Your Head' 
- Seemed appropriate. )

Brian - Good bye. Good luck. Good studying.
And goodness, please don't ask me for anything else until you've 
researched the topic yourself.

-Stu


==============================================================


On Nov 18, 2005, at 6:57 PM, Brian Heibert wrote:

> I find Stu Cram's example confusing (go figure)
>
> So whipped this up using TWM, FB & One of Ken's Scripts - Edit 
> Field-Parse Lines
> but how do I get what the user types after PRINT. If that gets working 
> that will help me alot
> in making other commands too.   Both Al Stafferri Jr. & I find Tokens 
> confusing (Stu's example)
>
> case "PRINT"
> PRINT theRest
>
<snip>