I was very excited about using the interprocess library to solve a set of problems in our current project, until I saw this post. We have to support 32 and 64 bit binaries. Falling back to using the low level utilities like mapped_region means that much of the appealing functionality from the interprocess library is unavailable to us. I understand that certain functionally between different sized address spaces doesn't make sense. A very large shared space from a 64 bit process would not be addressable in 32 bits. But I doubt that people are really using this library to share address spaces larger than 4 gig. More than likely developers want to share comparatively small amounts of data between processes. Is there any plan to add support for 32/64 bit in the future? Best, -- Allen Cronce On Apr 9, 2009, at 1:04 PM, Ion Gaztañaga wrote:
Stephan Menzel wrote:
The code is the same as in my 32 - 32 bit versions and known to work. Now I'm wondering, is this supposed to work or is 32 to 64 bit transfer not supported at all? Is this a bug or a feature? Do I have to have both applications in a 64 bit version?
There is no support for 32bit-64bit communications. You would need to use much lower level utilities, like mapped_regions to do that.
Internal structures have platform-dependent sizes (e.g.: offset_ptr needs to be bigger in 64 bit systems because it has to address much bigger address space). _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users