From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vfork and paging
From: rog@vitanuova.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20011002152706.3B01419A34@mail.cse.psu.edu>
Date: Tue,  2 Oct 2001 16:39:17 +0100
Topicbox-Message-UUID: fad85e60-eac9-11e9-9e20-41e7f4b1d025

> It is indeed true that you have to know what your program does.  With
> the thread library by default you share memory and fd's so accessibility
> doesn't change twixt light and heavy threads, though syncronization problems
> will be more likely to rear their ugly heads in the latter.

i was finding it difficult to debug rio, possibly because it has a
good mix of procs and threads and working out which function is being
called from what isn't too easy...

> I wrote ndb/cs and ndb/dns before the thread library and it was a bit
> of a pain.  I'le like to redo dns with it.

if i ever have to do multi-threaded code in C on another platform
again i shall port and use the plan 9 thread library - it's by far the
most reasonable i've seen.

i would miss the type checking on channels though.

i used to use occam, which had channels, but you could only use them
completely statically (no dynamic memory, no recursion, etc); the
possibilities afforded by dynamic channels are wonderful...; they make
some things so simple to implement.

  rog.