New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-6521 Add a Python interface with Log objects #11
Conversation
* one, or more comma-separated arguments. | ||
*/ | ||
#define LOGL_TRACE(logger, message...) \ | ||
do { if (LOG4CXX_UNLIKELY(logger.isTraceEnabled())) { \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are useful new macros, but maybe we can make them more useful :) In practically all other macros logger
means either LoggerPtr
(or Log
instance after your changes) or logger name (string). Can we do the same in the new macros to keep things consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the great suggestion. Done.
ef95111
to
1869cb1
Compare
d8f439f
to
9514896
Compare
a37d292
to
b5a32a7
Compare
Log's static functions were utility methods used in the custom interface that has been removed. For a more proper Log class, they should no longer be static. The API of the macros stays the same. The static setLevel(), getLevel(), and isEnabledFor() are removed. The static logMsg() and log() are kept because qserv needs coordinated changes before they can be removed.
b5a32a7
to
926eeb9
Compare
No description provided.