Scripting engine...

what i would suggest it to have the formatting of the script very rigid, have all the functions a set length (ie 4 characters long) and each command on a single line, hat way you don't have to bother with formatting the script.

here's what i would do:

-read line up to first space
-store data from read in cmd
-check if the command associated with cmd has paramters, if it does loop the number of pareters:
-read up to first space or carage return (ascii 10), or = or < etc.
-store data from read in p[ i ]
-end loop
-switch(cmd)
-case(...)
-do something
-case("if")
-if(p[1]=="="){
-if(p[0]==p[2]){
...}
....}
....
-end swithch
-go back to the beggingin until there are no more lines

i would also reccomend (although i'm no exprert) that you not allow conditinal statements to take up more than one line (like you can in c if you use {}), just to remove some comlexety from the scripting engine

hope this helps

Edited by - wingman20 on April 7, 2001 6:39:12 PM

I had the program go through recursively and grab a word (surrounded by parentheses or spaces), then I identified it (command, variable, built in function), and passed it on to the next word to be read. When I got to a semicolon I had a linked list going all the way to the right with everything identified, then I just went back through it (reverse), and did my stuff. I dunno if that helps, I''m pretty sure it doesn''t. If you''re looking for something fast, Flipcode has a good example of pre-compiled scripts.

============================
Trevor "Zephyre" Barnett