1. Oh no, I'm in over my head again
Hi,
I was just starting a big project that I probably can't handle alone: A
multithreaded interpreted language. Since I'm not *that* great at Eu pro-
gramming, it will probably look more like C or Java. Here's some sample code
that I thought of producing for the interpreter:
thread thread1 {
print(1,"Hello World\n");
}
thread thread2 {
for i = 1 to 1000 {
printf(1,"%d %x",i,i);
}
}
I've already finished the variable and token processing and function/proce-
dure registration functions. Anybody want in on this nameless project?
2. Re: Oh no, I'm in over my head again
What language will you use for the interpreter ?
Is it gonna be C, asm (wee!) or perhaps Lisp :) ?
Or why not write it in Java, that could be interesting..
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
3. Re: Oh no, I'm in over my head again
Well, it would be kinda hard to implement in asm, Java can't do everything
Euphoria can(if you're going to have graphics you'll have to give up file
access), and I don't know Lisp, so Euphoria was the natural choice.
Coding the token processing routines was especially easy because I down-
loaded "FaIkon1313's" eval() routine. The function doesn't calculate the
results of functions, but those should be evaluated before computeTokens()
is called.
Also, the variable naming scheme is reminiscent of PERL(a string might be
called $str, and integer could be called %thisint), though somewhat differ-
ent. Also, I'm afraid that given the number of times I've failed at creating
a language, it's not going to be that impressive. However, unlike before,
I'm splitting my work into several modules. Variable and token processing
routines go in vars.e, function and procedure calling routines go into
call.e,
threads go into threads.e, and the basic functions go into basics.e.
