Re: [Boost-users] Boost interprocess map in shared memory
Hallo Ion, it's perfect. It's working now very well. I have used the v 1.35 solution. I am planning to port the application to the HP-UX from Linux. Do you see any problems to use interprocess module 1.35 on that platform? Thank you, have a nice day, Jan Suchy Date: Fri, 30 May 2008 21:22:45 +0200 From: Ion Gazta?aga <igaztanaga@gmail.com> Subject: Re: [Boost-users] Boost interprocess map in shared memory To: Boost User List <boost-users@lists.boost.org> Message-ID: <48405405.7010801@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Jan Such? wrote:
Now, I want to have library, where i want to find previously created shared segment and read it more-times. But I do not want to open it on every runQ function call. I need to open this segment only once and use it more-times when runQ in lib is called.
I tried this:
The problem is that managed_shared_memory is not copyable. With current trunk code you could move it from localsegment to segment: managed_shared_memory localsegment(open_only, "MySharedMemory"); segment = move(localsegment); //localsegment is now in default-constructed state For 1.35 code allocate it through new (not compiled, this might contain errors): std::auto_ptr<managed_shared_memory> segment_ptr; int init() { segment_ptr.reset (new managed_shared_memory (open_only, "MySharedMemory") ); } Regards, Ion
participants (1)
-
Jan Suchý