You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Paul Dietrich (JIRA)" <ji...@apache.org> on 2016/03/19 00:26:33 UTC
[jira] [Created] (MYNEWT-262) Log module needs split in logging and
reporting
Paul Dietrich created MYNEWT-262:
------------------------------------
Summary: Log module needs split in logging and reporting
Key: MYNEWT-262
URL: https://issues.apache.org/jira/browse/MYNEWT-262
Project: Mynewt
Issue Type: Bug
Reporter: Paul Dietrich
Right now, each module using logs calls
log_register
This takes a log* and a log_handler*
However it should be up to the application to determine the log handler.
Really, the log registration should register a NULL handler by default
There should be a method in log.h
log_set_handler(char *logname, log_handler);
which would set the specific log to a specific handler.
That way, the module would not be making decisions about what type of logging the user wants.
We'd have to have some convention that a module would extern its
We are close with what we have now, except that you cannot re-register a log since its queue on the tail of a list. If we try to override the modules log settings.
Also , this would remove the packages dependence on console.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)