Re: [Boost-users] Library Interface Design
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Robert Kindred I can think of one example for not fully constructing objects: [snip] The problem is in starting up. If each one of these threads knows about each other via some method (pointer, or reference), then when a thread starts up its own business, whatever that is, then most likely it will start generating data and sending messages. When it tries to send a message to a thread that does not yet exist, BOOM!!! (yes, I have experienced this boom).
Can you not create them all, have them wait on some condition variable and signal when you're ready to go?
"Sohail Somani"
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Robert Kindred I can think of one example for not fully constructing objects: [snip] The problem is in starting up. If each one of these threads knows about each other via some method (pointer, or reference), then when a thread starts up its own business, whatever that is, then most likely it will start generating data and sending messages. When it tries to send a message to a thread that does not yet exist, BOOM!!! (yes, I have experienced this boom).
Can you not create them all, have them wait on some condition variable and signal when you're ready to go?
Yes, I suppose that works, with some extra effort. So does this mean that a monolithic constructor is very important to you? Robert Kindred
participants (2)
-
Robert Kindred -
Sohail Somani