On Oct 20, 2009, at 9:36 AM, Marcus Frenkel wrote:
Hi Jacob,
I propose that any new item in the global enum lists to be add at the
end, not in the middle. In example, for thread-safe operation we
cannot use enum gloox::ConnectionError in other thread, so we pass the
error as an integer using a safe way to the other thread. This
scenario requires continuous change in our code along with the changes
in the enum lists in newer Gloox versions.
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?
Note that we also can't use the enums directly because we're accessing
them through Objective-C, which can't include gloox.h (it includes C+
+), and can't handle the gloox:: namespace. But I'm working on
automating that issue by writing a script that converts the gloox.h
enums into C-friendly enums with a leading prefix. Perhaps this is
similar to your problem? I'm not looking for any changes to gloox
itself to handle this problem; it would make it too inconvenient for C+
+; I just want a better automated solution than our current manual
copying of the enums.
-Rob