rm5248 commented on PR #159: URL: https://github.com/apache/logging-log4cxx/pull/159#issuecomment-1349538359
My thinking is more along the lines of a first time user, having a small standalone example is very useful. Both spdlog and boost log have simple examples that are only about 10-20 lines long. I don’t think it’s a bad example(it is needed), I just think it’s a little complicated for the first example. Some of it depends on how you use the library - I always initialize the logging in main, because I can switch it around with a command line parameter. I also never log in a static initializer so there’s no need for me to load the config file before main starts. On Tue, Dec 13, 2022 at 1:10 AM Stephen Webb ***@***.***> wrote: > I changed index.md because I believe wrapping getLogger is a > best-practice technique. It will improve user code maintainability, > compared to initializing log4cxx in main. > > Why do you think have a wrapper fumction for getLogger is complicated? Is > it because you think a function local static struct is too complicated? > > I would expect level of software engineer using log4cxx (which is really > only appropriate for large applications) should be able to handle a local > static struct technique. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/logging-log4cxx/pull/159#issuecomment-1347796956>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAANWI6ZY2SWB5CLRNXBHMLWNAHOPANCNFSM6AAAAAAS3TSDZI> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- 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]
