[m-dev.] for review: changes to runtime required for webserver
Peter Ross
peter.ross at miscrit.be
Wed Aug 23 06:36:39 AEST 2000
On Tue, Aug 22, 2000 at 08:48:41AM +1000, Robert Jeschofnik wrote:
> On 21-Aug-2000, Peter Ross <peter.ross at miscrit.be> wrote:
> > Hi,
> >
> > For anyone to review.
> >
> > ===================================================================
> >
> >
> > Estimated hours taken: 2
> >
> > Changes required to the Mercury runtime so as to build the webserver
> > written by Peter Ross.
> >
> > runtime/Mmakefile:
> > Add the new semaphore files.
> >
> > runtime/mercury_semaphore.h:
> > runtime/mercury_semaphore.c:
> > Add an implementation of semaphores written by Tom Wagner for
> > pthreads. The only changes made to the code was so that it obeys
> > the Mercury C coding convention.
>
> What about the semaphore stuff that Tom Conway has allready done, and is in
> extras/concurrency ?
>
AFAICT the semaphore implementation of Toms is tied quite heavily with
the representation of Mercury `threads', so is not usable in the hlc.gc
grade. When I get my stuff more sorted I plan to start integrating it
with Toms work, at the moment it is at the proof of concept stage.
> or is this for genuine posix threads, and not just threads inside the one
> mercury engine?
> (if so, this could be exactly what I am after for something else I was doing)
>
It is for genuine posix threads (what is a non genuine posix thread, by
the way ;) ), each spawned thread is run in its own posix thread.
The next step in my plan is to start using the Win32 thread primitives.
Should be fun.
Pete
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions: mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------
More information about the developers
mailing list