Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!rbj
From: rbj@uunet.UU.NET (Root Boy Jim)
Newsgroups: comp.lang.perl
Subject: Re: anyone gotten mmap to work w/ perl?
Message-ID: <129281@uunet.UU.NET>
Date: 16 Apr 91 20:32:04 GMT
References: <535@appserv.Eng.Sun.COM> <1991Apr9.051702.22978@jpl-devvax.jpl.nasa.gov> <28046072.4CFC@tct.com>
Organization: UUNET Communications Services, Falls Church, VA
Lines: 20

In article <28046072.4CFC@tct.com> chip@tct.com (Chip Salzenberg) writes:
>According to lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall):
>>What you'd really kinda like is a way to mmap a particular variable, and
>>let Perl worry about it when it gets reallocated...
>
>If such a thing were done, we we would get shmat() for System V IPC
>almost for free.

As it should be. I have already complained that shm{read,write}
detach the shared memory segment between accesses. The implementor
wrote back and said he did it that way just to get it to work, but
didn't really understand how to do what Larry suggested.

Which brings me to perl's code itself. Can anybody suggest how
to approach perl's internals? What order should I read the files?

It's a pretty hairy program, much harder to read than emacs.
-- 
		[rbj@uunet 1] stty sane
		unknown mode: sane