According to Orlando Llanes:
[...] I found Lex/Yacc for TP on ieec.com(?), it was a version from the "Dragon Book" [...]
I know this is a stupid question but what is the title/author/foobar of this famous "Dragon Book"? I really have the impression that I should read it ...
Below are the specs for the script object followed by the reasons for the specs and then my plans for the script executor object..
What is the aim of this scripting language? You are probably not going to reinvent Pascal or Java. I assume that you want to have a language that allows the user to customize and extend the behaviour of your program. Did you have a look at GUILE, GNU's answer to this question? (I haven't, but I have read a lot about GUILE's existence.;-) Or else, what about defining a CGI-like interface between your program and another program written by the user in his/her favourite language?
[...] I'm planning on doing this is by allowing the programmer to add tokens of their own to the script language at run-time.
What is the difference between this and the concept of user-defined types, variables, and procedures?
Now for the script executor object. I want to have a fixed set of baseopcodes so that no matter what language the scanner is written to handle, it will always execute the opcodes in the same way, this way 2 or more script scanners can be written to cater to the tastes of the end-user, but will execute the same.
The GNU compilers also support such a platform-independent "bytecode", and so does UCSD's P-Code and Java's J-Code. Perhaps you should have a look at their specifications first? Those of GCC/GPC are in the source code.
Greetings,
Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/