Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!bellcore!uunet!jarthur!usc!ucsd!nosc!crash!ncr-sd!serene!briand
From: briand@rfengr.com (Brian Dear)
Newsgroups: comp.sys.next
Subject: Re: NeXT equivalent of Shared Memory and Semaphores on SysV
Keywords: Shared Memory
Message-ID: <1991Feb22.044136.2498@rfengr.com>
Date: 22 Feb 91 04:41:36 GMT
References: <1991Feb21.152540.10679@noose.ecn.purdue.edu>
Reply-To: brian@coconut.com
Distribution: usa
Organization: Coconut Computing, Inc., La Jolla, California
Lines: 23


Good to hear I'm not the only one who needs shared memory on the NeXT.
I too need shmget(), shmat(), shmdt(), etc BADLY for some code I'm porting
to the NeXT environment.

Anti-AT&T System V UNIX gurus may scoff, but the System V shared memory
routines have been a joy to use and are, above all, _simple_ to implement.
I haven't figured out an alternative yet for NeXT.  If Mach's so great,
how come it's so difficult to implement a simple shared memory setup like
you can do in UNIX System V?

Any suggestions from knowledgeable Mach programmers would be *greatly*
appreciated.   It would be ideal if a publicly-available set of routines
were available that either mimicked or emulated the System V shared memory
routines.    

I'd even be interested to hear about commercially-available routines
that can be used on the NeXT to do this.  

-- brian


Brian Dear              brian@coconut.com            Coconut Computing, Inc.


Brought to you by Super Global Mega Corp .com