[
https://issues.apache.org/jira/browse/MYNEWT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sterling Hughes updated MYNEWT-262:
-----------------------------------
Fix Version/s: (was: v0_9_0)
v0_10_0
> 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
> Assignee: Vipul Rahane
> Fix For: v0_10_0
>
>
> 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)
