Re: [Boost-bugs] [Boost C++ Libraries] #4827: Windows vs POSIX interface distinction seems unnecessary

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4827: Windows vs POSIX interface distinction seems unnecessary
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-04-02 20:15:50

#4827: Windows vs POSIX interface distinction seems unnecessary
-------------------------------+--------------------------------------------
  Reporter:  psiha             |       Owner:  igaztanaga  
      Type:  Tasks             |      Status:  reopened    
 Milestone:  To Be Determined  |   Component:  interprocess
   Version:  Boost 1.44.0      |    Severity:  Problem     
Resolution:                    |    Keywords:              
-------------------------------+--------------------------------------------

Comment (by igaztanaga):

 Interprocess insists on the POSIX model because it is the portable way
 that can be reliable and easily implemented in all OS and with all users.
 That's one of the main goals for all Boost libraries. In Interprocess
 review this was decided and it is not going to change. Windows reference-
 counted semantics are imposible to achieve reliably in POSIX (a process
 crash would leave the memory permanently) without kernel help and windows
 persistent shared memory needs special priviledges. So there is no
 discussion here.

 windows_shared_memory offers referece-counted semantics because they are
 useful for Windows users. Using OBJ_PERMANENT might be useful to implement
 shared memory for users accepting priviledge limitations, but not as a
 general solution.

 I'm sorry we don't share views on the library design but there is nothing
 we can do about it.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4827#comment:10>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.