| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
also changed some of `InvalidOperation` cases to
`MemorySegmentError` as it should be basically generic enough at the
base class level.
|
|
|
|
|
|
regarding the case where the segment has grown due to the allocation.
|
|
|
|
Also make a minor typo fix.
|
|
|
|
|
|
|
|
also clarify these in doc.
|
|
|
|
|
|
|
|
committing mostly as a backup.
|
|
See bug #2367 for the fix-scaffolding.py tool.
|
|
|
|
what was allocated
|
|
|
|
|
|
|
|
These could very well not be the implementations we are looking
for. From the bug report, it's not clear how these methods will be used:
* Is deallocate() meant to free smaller blocks than what allocate()
returns?
* Because these methods will be virtual, a MemorySegment object is
necessary. Will this be a singleton?
* Does allMemoryDeallocated() need anything fancy like a set of all
allocated buffers kept, or is just a counter of total size of memory
allocated sufficient? (The counter is implemented.)
|