Re: [D] Next Log4cxx Major release thoughts [logging-log4c xx]
swebb2066 (via GitHub) <[email protected]>
| Newsgroups | gmane.comp.jakarta.log4j.devel |
|---|---|
| Message-ID | <ghd-D_kwDOBToI6s4AhRe1-01bff5f8-f35f-453d-80c8-830598ade3ac@gitbox.apache.org> |
GitHub user swebb2066 edited a comment on the discussion: Next Log4cxx Major release thoughts I had previously thought we could provide users performance benefits without any code change by introducing asynchronous loggers as the default. I have since realised this would not be a good idea because: 1. Buffered asynchronous logging creates confusion during development as the log file may not contain the most recent logging events (when the debugger stops the application or std::terminate is called) 2. The LOG4CXX_XXXX_ASYNC macros introduce significant code bloat (approx 200 bytes per log request) compared to LOG4CXX_XXXX macros. Given I do not see a technical need for a new ABI arrizing soon, one option we have would be to relabel the 1.6 features as 2.0 and bump the ABI version now. Thoughts? GitHub link: https://github.com/apache/logging-log4cxx/discussions/519#discussioncomment-15055839 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]