Re: Why are memory-mapped storages read-only?

The mmap functionality was implemented to allow access to
large data files without having to explicitely load them
into RAM in advance. Back in the old days of Solaris, if 
you mmapped in read-only mode, the swapping system was
smart enough to never swap out. Hence you would save
a lot on disk (or network) bandwidth.

Also, you really don't want a random bug in a Lush program 
to inadvertently corrupt your dataset file on disk......

That said, we could have two types of mmapped storages:
one for read only, and one for read/write.

  -- Yann

Leon might remember. I seem to rememberthink writing to mmapped storages
used to crash on Solaris 

On Wednesday 02 September 2009, Ralf Juengling wrote:
> Hi,
>
> Does anyone remember why lush does not allow to
> manipulate memory mapped storages?
>
> Ralf
>
>
> ---------------------------------------------------------------------------
>--- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day trial. Simplify your report design, integration and deployment - and
> focus on what you do best, core application coding. Discover what's new
> with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Lush-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lush-devel



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july