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) |
Newsgroups: | comp.compilers |
From: | bosullvn@vevey.serd.cscs.ch (Bryan O'Sullivan) |
Keywords: | interpreter, design |
Organization: | SeRD, Swiss Scientific Computing Centre |
References: | 93-10-023 |
Date: | Mon, 4 Oct 1993 12:24:33 GMT |
David Randolph Conrad <davidc@iij.ad.jp> writes:
> 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.
I wanted to do something similar several months ago and hunted around to
no avail. I ended up writing a threads package (the system I was using
was pretty obscure) and making Tcl sit on top of it (I didn't have to
modify Tcl in any way).
I'd be of the opinion that you might be better off to do more or less what
I did, and sit Python, SCM, or some other embeddable language on top of a
threads package (pthreads would seem to be a good candidate, since
implementations of it are now fairly widely available); I find that this
approach allows me to use any potential concurrency `properly', and saves
the effort of trying to hack together something which gives much the same
effect.
<b
--
Bryan O'Sullivan email: bosullvn@serd.cscs.ch
Research and Development Section work: +41 (91) 508 232
Swiss Scientific Computing Centre fax: +41 (91) 506 711
(also Trinity College, Dublin, Ireland) home: +41 (91) 712 573
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.