[interprocess] shared_memory_object design
27 Aug
2009
27 Aug
'09
2:19 p.m.
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
5559
Age (days ago)
5559
Last active (days ago)
0 comments
1 participants
participants (1)
-
Christian Henning