In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Coriolis wrote: Ill try to be more explicit. You cannot use my code to come out with a Forth interpretor for sale without setting up a royalty schedule. However I have no problems with you using it to generate firmware within an application, an end program in a commercial application is fine, no royalties. But a commercial venture to provide the capability of others to create Forth programs would require some negotiations. Now with that said, this is very much a work in progress. There is one crucial portion missing which would be nessesary to produce a viable Forth engine, and thats the compiler. Right now in order to create a Forth program, you must hand tokenize the commands according to the token table and place those tokens in a data table in the SX's memory. I understand this makes the process tedious at best. The compiler would be a PC resident program which would tokenize the Forth code and spit out a program with the token code and the interpretor. I originally envisioned the compiler would dynamically create a token map according to the actual Forth code and incorporate only those Forth commands used by the program, allowing maximization of the token space for user programs. You are welcome to peruse my code and decide if you want to run with it, I can lend my advice on interpretation of the code within the interpretor and verbal help with creation of a compiler, free of charge. If you decide to use the code, want a compiler, and don't want to write it yourself, we can enter negotiations on cost of me developing the compiler and IP issues on the compiler and interpretor (whether you want control of the rites to both, or not). ---------- End of Message ---------- You can view the post on-line at: http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=93686#m93798 Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)