vopl commented on PR #277: URL: https://github.com/apache/logging-log4cxx/pull/277#issuecomment-1786845305
> Is this to fix a problem that you have encountered before? I'm wondering because having the ABI stable(with version 1.0.0 and above) should help fix that problem. All commits from this pull-request are targeted to а possibility, declared at first message here: https://github.com/apache/logging-log4cxx/pull/277#issue-1966976922 ABI keeps stable and not changed by default, but totally changed if `LOGCXX_NS=log4cxx' CMake variable changes, and this is a wanted goal - allow to use more then one ABIs from different loggers in moment without any conflicts. > Could you add some documentation on how to use this feature? And ideally when you would use this feature. My documentor-skills are very bad :( The central changer here is LOGCXX_NS variable. If it has a value 'log4cxx' (default), then all happens as before, no changes. If LOGCXX_NS=somecustomname, then all log4cxx entities are placed in that 'somecustomname' namespace instead of 'log4cxx'. This allows to use two and more logger instances simultaneously, for example, 'some old plugin X' uses log4cxx instance from local system, central application uses own log4cxx with LOGCXX_NS=xyz, other plugin uses thrid log4cxx instance with LOGCXX_NS=qwe. All components are not constrained by each other an now and can made an unrestricted (by other parts through log4cxx) development progress. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
