Subject: [boost] [Interprocess] Managed mapped file questions
From: Jorge Lodos Vigil (lodos_at_[hidden])
Date: 2012-12-10 15:15:19
First of all, thank you for boost interprocess :-)
I have a couple of questions:
1. When you grow a managed mapped file, the current implementation fills all the new space with zeroes. This is less efficient than just resizing the file. The comments in the code implies there is a reason, so what is it?
2. When the size to map is too small, take 1 or 2 bytes for instance, the library fails in a non elegant way. This is a corner case, but I could not find this documented. Is this a bug?
I'm asking this before sending any sample code or creating tickets, but of course I could do that as well if there is the need.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk