Portability in my review of the code is based on Linux/BSD/UNIX and
not with other systems.
I would like to see diffs of changes. By the way, I only run svn co
... to compile a new version.
If it works out, I flip the previous version with the current and wait
the next update.
Regards
*
Leslie
*
*Leslie Satenstein*
*Montréal Québec, Canada*
**
------------------------------------------------------------------------
*From:* Blake McBride <address@hidden>
*To:* address@hidden
*Cc:* GNU APL <address@hidden>
*Sent:* Tuesday, May 16, 2017 7:51 PM
*Subject:* Re: [Bug-apl] 950 )HELP Issue, and mem.cc
On Tue, May 16, 2017 at 2:30 PM, Fred Weigel <address@hidden
<mailto:address@hidden>> wrote:
...
Find attached a first cut at shared memory support (mem.cc). It
allows mmap() ...
A friendly plea to remain portable. I've seen it time and again, a
great, portable software package comes out. And then they start
tweaking it peace by peace until, for largely no reason, it becomes
unportable and unmaintainable. In 35 years, I've not needed memory
mapped files (but I understand that that may be due to the kinds of
problems I faced). Still, I hope an eye is kept on simplicity and
portability. I wouldn't start adding all sorts of cute stuff.
Just my two cents.
Blake