[Boost-users] [interprocess] shared_memory_object design

Hi there, a colleague of mine is questioning the design decisions in the shared_memory_object class. The assignment operator and copy constructor are private. Why? Also the constructor takes a type instead of a value as the first parameter. In his eyes it makes it very inflexible since the creation of or attaching to shared_memory area has to known at compile time. A few pointers on why such a design was chosen would be very helpful. Regards, Christian