Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: perl and shared memory ?
Keywords: perl shm shared shm SysV
Message-ID: <1990Sep25.172747.17739@iwarp.intel.com>
Date: 25 Sep 90 17:27:47 GMT
References: <1371@nixsin.UUCP>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 25
In-Reply-To: koerberm@nixsin.UUCP (Mathias Koerber)

In article <1371@nixsin.UUCP>, koerberm@nixsin (Mathias Koerber) writes:
| Is there a possibility for perl to access sysV shm segments?
| Maybe treated as a file, or via some calls or so?
| If not, would Larry consider implementing it? I'd like to use perl
| to monitor the contents of my shm segments, instead of having
| to write a C-Program for everything.

Hmm.  I was just polishing up those sections for The Book.  Consider
your request fulfilled by Perl 4.0, available Real Soon Now.  The
coding was provided by someone who's name escapes me at the moment,
and Larry dropped it into the main code.

The new operators that deal with shared memory are shmctl, shmget,
shmread, and shmwrite.  And you also get msgctl, msgget, msgrcv, and
msgsnd.

Not being a big sys V fan, I don't know how useful all that stuff is,
but some of you are going to like it. :-)

print "Just another ", "System V "&&"", "Perl hacker,"
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/