but howto protect your pointer ? Also, mmap-ed spaces can hardly be GCed, this will introduce extra complexities.
still see no extra necessary in compare to ports. On Tue, Apr 30, 2013 at 10:23 PM, Nala Ginrut <nalagin...@gmail.com> wrote: > On Tue, 2013-04-30 at 21:57 +0800, Daniel Hartwig wrote: >> On 30 April 2013 21:49, Nala Ginrut <nalagin...@gmail.com> wrote: >> > If I use bytevector instead, it means I have to read all the content >> > from a file first. I don't think it's the same with mmap in POSIX. >> > mmap is used for very large data I/O, if we decide to read them all, we >> > lose the game. >> > mmap does lazy disk I/O automatically for the file. >> > >> >> With the pointer that mmap returns you can pointer->bytevector. This >> will not read any of the file. > > Ah~nice! That's the critical hint to reduce the work. > Yes, after mmap, we don't need other things anymore. > But I still recommend that store 'size' & 'flags', which need a new > record-type and to write some helper functions, but very less code. > > What other guys think? > > And I'm amazing by the cool of Guile, again. ;-P > Thanks! > > >
