embeddable threaded interpreted language

David Randolph Conrad <davidc@iij.ad.jp>
Mon, 4 Oct 1993 05:22:08 GMT

          From comp.compilers

Related articles
embeddable threaded interpreted language davidc@iij.ad.jp (David Randolph Conrad) (1993-10-04)
Re: embeddable threaded interpreted language bosullvn@vevey.serd.cscs.ch (1993-10-04)
Re: embeddable threaded interpreted language sdm7g@elvis.med.virginia.edu (Steven D. Majewski) (1993-10-05)
| List of all articles for this month |

Newsgroups: comp.compilers
From: David Randolph Conrad <davidc@iij.ad.jp>
Keywords: question, interpreter
Organization: Compilers Central
Date: Mon, 4 Oct 1993 05:22:08 GMT

I may not be using the proper terminology (I'm a network weenie, not a
compiler weenie), if so, my apologies. I'm looking for a small embeddable
interpreted language for an application I am writing. The catch is that
my application has better things to do than sit and wait around for the
language interpreter to finish. Specifically, I would like a language
where I can have multiple "threads" do:

rc = interp( state, code, time_slice )

and the interpreter will execute 'code' for at most 'time_slice' steps
(seconds, whatever). All the code for embeddable languages I've seen to
this point have been "run till the end of the code" types like icon, tcl,
perlv5, etc. My first thought was to write a p-code translator and
interpreter, but I'm hoping I don't have to reinvent the wheel.

I'm not too particular about the syntax, etc., although I would prefer
something C-like. Since I'm planning on making my application publicly
available, I'd only be interested in freely redistributable code. Anybody
have any pointers to something that might help? Please send mail, and
I'll summarize...


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.