🚀 go-pugleaf

In article <1165@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
> Rather depends on what you mean by a system call and IPC doesn't it? The
> programmer need not concern himself that IPC is happening as the result of a
> system call, nor does he need to handle messages just because the system is
> using them behind his back.

(hyperventilating) We're not talking about what the programmer sees.

(calmer) Or at least I'm not. The point is what the system sees. All that
IPC makes resource tracking a harder problem than it is in UNIX. When a program
exits, the system really has no way of knowing whether it can safely free
any resources allocated by that program or not.

> Perhaps so.. a system call is a system call. That it generates a message or a
> series of messages is beside the point.

No, that it generates a series of messages or otherwise has to coordinate with
other processes is *precisely* the point. Even line drawing, through the layers
library, has to be co-ordinated...
-- 
 _--_|\  Peter da Silva <peter@sugar.hackercorp.com>.
/      \
\_.--._/ I haven't lost my mind, it's backed up on tape somewhere!
      v  "Have you hugged your wolf today?" `-_-'