|
On 15/01/2013 7:45 AM, Hadriel Kaplan wrote:
and had considered making all of our pushed C++ objects derive from a common base that had a member variable for a 'serial number': a number which is unique for every C++ object for all time.[**] The pushed object in Lua would have a copy of this serial number, and would be checked against the C++ object's serial number on every method call.
How do you handle the case where allocator causes the allocated page(s) to be unmapped? or do you ensure that the pages are never unmapped?
Ross.