[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #54788] Implementation of memmapfile
From: |
Guillaume |
Subject: |
[Octave-bug-tracker] [bug #54788] Implementation of memmapfile |
Date: |
Fri, 11 Sep 2020 13:04:26 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 |
Follow-up Comment #2, bug #54788 (project octave):
Adding a link from bug #58953 that might be useful to deal with m.Data(end):
https://stackoverflow.com/questions/23016606/what-are-the-semantics-of-end-in-matlab/23017087#comment35192810_23017087
The issue here is that m.Data(end) will first evaluate m.Data, i.e. read the
entire mapped data into memory and then return its last value, defeating the
point of memory mapping.
Or is it that the dependent property Data should contain an object from the
__memmapfile_handle__ handle class (instead of private property MemoryMap) so
that an end() method can be implemented in that class?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?54788>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #54788] Implementation of memmapfile,
Guillaume <=