Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!think!ames!sun-barr!decwrl!shelby!polya!rokicki
From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Static limits (Re: AmigaDos directory knowledge + (new) BENCHMARK I DID)
Message-ID: <12944@polya.Stanford.EDU>
Date: 7 Dec 89 09:23:52 GMT
References: <4669@sugar.hackercorp.com> <807@jc3b21.UUCP> <4685@sugar.hackercorp.com>
Organization: Computer Science Department, Stanford University
Lines: 16

peter@sugar.hackercorp.com (Peter da Silva) writes:
> Meanwhile, sharing sigbits is pretty scary stuff. Even with CloseWindowSafely
> debugged, you can get GURUs pretty easily.

Explain.  I share sigbits trivially.  Especially just associating a signal
with multiple message ports.  Signals are like interrupts, and shared in the
same way; explain how you can do the same with fd's.  (Just the base case;
sharing an fd between two files . . . what, you close and reopen all the
time?)

Signals are actually quite nice.  You give the first five signals to your
five most common events, and then the rest are probably uncommon enough
where they can all share the same signal bit.  Multiple signal bits to me
are just a convenience . . .

-tom