Re: [boost] [FSM] Review library version update

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe
AMDG
Andrey Semashev <andysem <at> mail.ru> writes:
Yes, you're right here. But there's nothing really dangerous in running state_dispatcher constructor more than once
concurrently. I'll
see what I can do about it, just to be on the safe side.
This has exactly the same problem that m_StatesInfo had. It can be used before it is initialized.
Is there interest in having a boost singleton? A preliminary implementation of it could use boost::once. Then all lazy initializations would happen through that interface. Just a thought. Sohail

Hello Sohail, Tuesday, February 6, 2007, 1:08:25 AM, you wrote:
Is there interest in having a boost singleton? A preliminary implementation of it could use boost::once. Then all lazy initializations would happen through that interface.
Just a thought.
I think a generic implementation of a thread-safe singleton is a nice idea. I encounter this problem quite often. Although, once-based implementation doesn't suit me very well in this case. -- Best regards, Andrey mailto:andysem@mail.ru
participants (2)
-
Andrey Semashev
-
Sohail Somani