OpenEuphoria

Re: Threads......

• Posted by gertie at ad-tek.net Jul 05, 2001
• 398 views

On 5 Jul 2001, at 21:33, Jeffrey Fielding wrote:


> 
> But Euphoria is non-reentrant... I tried writing a thread library for
> Euphoria on linux. call_back worked okay for interfacing with pthreads, but
> since Euphoria is non-reentrant, the program didn't work very well.

What if the thread was to exec an instance of the interpreter with the thread's
code as
the run parameter? Then the interpreter wouldn't need to be reentrant, and if
the
structures that are set up by the thread calls were in the same memory space
that the
thread handler set up, everything could work peachie keen, yes? The Eu program 
could access the structures, know it's ident, and talk to the thread api
properly?

Kat

> Jeff
> ----- Original Message -----
> From: <euman at bellsouth.net>
> To: "EUforum" <EUforum at topica.com>
> Sent: Thursday, July 05, 2001 10:18 PM
> Subject: Threads......
> 
> 
> >
> >
> > Threads are impossible for me useing strictly Euphoria.
> >
> >      -- start threads
> > hThread1 = call_back(routine_id("Thread1"))
> > hThread2 = call_back(routine_id("Thread2"))
> >
> > hThread1 = c_func(xCreateThread,{NULL, NULL, hThread1, NULL,
> > NORMAL_PRIORITY_CLASS, thread1})
> > hThread2 = c_func(xCreateThread,{NULL, NULL, hThread2, NULL,
> > NORMAL_PRIORITY_CLASS, thread2})
> >
> > The call_back address is not a *real* proc address
> >
> > I will have to create a .dll for use, useing Masm32 or Borlands C++.
> > I need to learn a few things to do this so no-one hold their breathe.
> >
> > Something like this would be more valuable than namespace
> > in my opinion.
> >
> > Later,
> >
> > Euman
> > euman at bellsouth.net
> >
> >
> >
> >
> >
> >
> 
> 
> 
> 
>