On Mon, Jul 26, 2010 at 4:44 PM, Jay K <[email protected]> wrote: > > > Merging libpthread into libc is the way imho. > > That would make it somewhat difficult to work on a second pthreads > > library... > > Like a second C library..
No, not really. You see, we aren't working on a second C library, but we *are* working on a second threads library. > The benefit of having only one is a smaller system and better interopability: Don't worry, since you're not working on the second library, you don't have to care. Meanwhile, those reasons are useless to me. Heck, right now, they do interoperate. I'll probably break that at some point to eliminate some limitations and there will be tremendous wailing and gnashing of teeth by various people, to which the response will be "past or future: take your pick". <...> > And the current semantics where there are no kernel threads (right?), > probably not ideal or desired for long. So you know that, but you still wrote to suggest that we merge libpthread into libc? Nice. Philip Guenther
