anonymous — Sat, 11 Oct 2014 17:54:29 GMT

But isn't just a problem of file naming convention ? Technically you can specify the name of the shared object ... and it's not decorated at all by boost. Could you give me an example ... isn't just because you changed compiler between both and allocate string instead of array of char ?

Yochai Timmer — Fri, 24 Oct 2014 08:33:57 GMT

The folder name is different, and in the older versions the file name was decorated by boost.

Create 2 projects, a DLL and an executable. Link one project to boost 1.54 or older (i used 1.51), and the other to boost 1.55.

Then use the exact same code (different classes for a different name, the fact that you cant use the same shared memory object is another issue).

//in Dll1
struct Test1
{
static void OpenSharedMemory() { boost::interprocess::message_queue sh(boost::interprocess::open_or_create, "Test1", 20,24); }
}
//in The executable
struct Test2
{
static void OpenSharedMemory() { boost::interprocess::message_queue sh(boost::interprocess::open_or_create, "Test2", 20,24); }
}

Now call them in the main function, the second call will always fail (you can change the order).

int main(int argc, char* argv[])
{
Test1::OpenSharedMemory();
Test2::OpenSharedMemory();
return 0;
}

Boost C++ Libraries: Ticket #10581: Conflict when using boost::interprocess objects when linking to 2 different boost versions