Thursday 15 April 2010

c++ - Are shared memory segments compatible across boost versions and compiler versions -



c++ - Are shared memory segments compatible across boost versions and compiler versions -

i'm maintaining old project, , has work project build newer version of visual studio , newer version of boost. communicate other processes, first project uses shared memory segment, sec project has read segment (and write it) not create it.

is possible? there restrictions? don't seem find documentation it.

boost versions involved: 1.35 , 1.55 (it might updated 1.56) visual studio versions: 8.0 , 2013.

this interesting question.

on library level, i'd assume no breaking changes exist unless document.

however, there many more things take account.

you sharing memory

this implies you're straight sharing memory representations of classes.

this implies:

implies:

you sharing abi

this rules out compatibility if happen utilize different compiler flags, the same compiler/library versions.

in other words, don't share memory unless command both ends , can create sure binary compatible.

summary

boost's shared memory offerings nothing info representation (beyond "if can link same binary, it's plenty ipc access"). so, if need level of isolation, at

boost serialization combine eos portable archives bigger portability

c++ visual-studio boost ipc shared-memory

No comments:

Post a Comment