At 12:56 AM 9/18/2001 +0300, Jarkko Hietaniemi wrote:
>On Mon, Sep 17, 2001 at 05:54:41PM -0400, Dan Sugalski wrote:
> > At 12:51 AM 9/18/2001 +0300, Jarkko Hietaniemi wrote:
> > > > > Doug Lea's malloc is in the public domain:
> > > > >
> > > > > http://g.oswego.edu/dl/html/malloc.html
> > > > >
> > > > > I don't remember whether that's quadsafe code but the first person to
> > > >
> > > > It is.
> > > >
> > > > Further digging found this comparison discussing malloc and gc
> > > > implementations:
> > > >
> > > > http://www.cs.colorado.edu/~zorn/Malloc.html
> > >
> > >Whichever GC implementation we choose and/or write should be not just
> > >quadsafe, but threadsafe, too. Ouch.
> >
> > Luckily we don't have to have the GC be threadsafe as such, if we're
>
>There shall be No Way Ever for the user to use platform native threads
>(just to complete their hobbies in addition to juggling live chainsaws
>and electric eels)?
No, rather the threads will GC only those variables they own, and all
memory movement of shared variables will require the variable's lock to be
aquired first. Memory pools will generally be thread-private, though shared
variables might allocate out of the shared memory pool.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
