Thread pause and resume
Sean Kelly
sean at invisibleduck.org
Mon Apr 6 11:50:19 PDT 2009
== Quote from Steve Teale (steve.teale at britseyeview.com)'s article
> Sean Kelly Wrote:
> > == Quote from Steve Teale (steve.teale at britseyeview.com)'s article
> > >
> > > In some code I wrote at that time, I had a worker thread pool. When a thread had done its job it would mark itself as
available then
> > pause. The listener thread would then resume it or start one that had never been started. I'm trying to get it running in
2.26. There
> > are functions of the same name there but they are nested inside SuspendAll and ResumeAll, and so not accessible.
> >
> > This sounds like a classic producer/consumer case. I suggest using condition
> > variables (core.sync.condition with core.sync.mutex).
> The problem is at the moment, that the D documentation covers the language, and Phobos - the latter option exposes Object
to some extent.
> Anything that is in core.* is undocumented and you have to 'rtfsc' - if you can find it. I can't even find "core.sync" in D files
under dmd. Can you point me in the right direction please.
Darnit... core.sync is supposed to be in src/druntime/import/core/sync, but it isn't
there for some reason. I thought this issue had been fixed. Well, in theory it should
be there, and I'm working on getting the docs integrated with the Phobos docs. They're
already generated by the build...
More information about the Digitalmars-d
mailing list