I have not attempted to compile the new code with any Visual C++ compiler yet, so there is a possibility that there will need to be some small compatibility tweaks which would happen sometime tomorrow.
Would appreciate any testing or feedback.
I just committed an almost complete replacement of AsyncAppender with
a port from the current log4j sources (see bug https://
issues.apache.org/jira/browse/LOGCXX-129). There is still some
funkiness in the unit tests. testBadAppender that tests how
AsyncAppender recovers from an exception thrown by the nested
appender failed and is disabled and testConfiguration has much of the
test commented out as there are problems getting a reference to the
nested appender from the async appender. Will need to track down
both of them, but they should not not seriously affect the usability
of the appender in its current state.
