**gloox::ConnectionError::ConnDnsError is just a constant enum value that
can never change. I don't see why that isn't thread-safe? ...
On Tue, Oct 20, 2009 at 2:51 PM, Marcus Frenkel <marcus.frenkel@xxxxxxxxx>wrote:
>
> On Tue, Oct 20, 2009 at 3:56 PM, Rob Napier <rnapier@xxxxxxxxx> wrote:
> >
> > On Oct 20, 2009, at 9:36 AM, Marcus Frenkel wrote:
>
> > Marcus, can you explain better what you mean by "for thread-safe
> operation
> > we cannot use enum gloox::ConnectionError in other thread?" Why is there
> a
> > problem using this symbol?
>
> I wanted to say that more threads can access the same value at the
> same time. If we use something like:
> if (error == gloox::ConnectionError::ConnDnsError)
> in multiple threads at the same time, I think, theoretically it can
> cause an issue.
>
> Marcus
>
>
>
> --
> gloox-dev mailing list
> to unsubscribe:
> send a message with subject 'unsubscribe gloox-dev' to
> minimalist@xxxxxxxxxx
>