Re: Embeddable and Extensible Languages

PlayDough wrote:


[...]


> Nearly all the languages I've looked at have some soft of global,
> static storage that prevents this type of mechanism from working. For
> example, Ruby has ruby_init(). Ignoring issues of callback (language
> extensions that call class methods), is there a language that
> guarantees that x1's interpreter and x2's interpreter will not collide
> in threads?


See Chez Scheme's notion of 'waiters' and 'cafes'. Also see
"call-with-current-continuation." It's a little hard to get your head
around at first, but with it you can build whatever kind of threading
suits your application. Really powerful stuff.


-thant
--
"When fascism comes to America, it will be wrapped in the flag and
carrying the cross." -- Sinclair Lewis, "It Can't Happen Here" (1935)

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