Given that the mapped file content is not part of the library interface, and the only expected user of the mapped file is the library itself, why waste time in Windows? Seems to me that a requirement that files should be identical is too strong, as long as they work and
El 13/12/2012 2:28, Jorge Lodos Vigil escribió: perhaps don't affect platform portability. File portability between platforms should be warranted? What about platforms with different endianness? I just remembered that for initialization issues, at least the first bytes of the segment are supposed to be zero (POSIX guarantee) when first created. This zero value is used for some atomic operations to avoid racing conditions between simultaneous creation calls from different processes or threads. Maybe there is a way to guarantee the zero fill just for the first bytes of the underlying object and avoid it for the rest of the object. Best, Ion