[jira] [Commented] (MYNEWT-262) Log module needs split in logging and reporting

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MYNEWT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472537#comment-15472537 ] 

ASF subversion and git services commented on MYNEWT-262:
--------------------------------------------------------

Commit 1fd3fbfe068ed496b92523185a093ecee7c52164 in incubator-mynewt-core's branch refs/heads/develop from [~peterfs]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1fd3fbf ]

Logging format and initialization

MYNEWT-368: Complete logging format changes including saving log format version in fcb struct in flash

MYNEWT-262: Move initialization of logging resources to application. Logging handler is chosen by application and uses standard log_handlers rather than having each app call the handler_init function. Per-instance log structure are declared and initialized in each app and are associated with the log calls by log_register. Separate notion of log "type" for newtmgr (i.e, stream, memory,storage), and how log records are handled (e.g, cbmem, fcb).

Also - fix console_print_prompt() warning, nffs logging


> Log module needs split in logging and reporting
> -----------------------------------------------
>
>                 Key: MYNEWT-262
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-262
>             Project: Mynewt
>          Issue Type: Improvement
>            Reporter: Paul Dietrich
>            Assignee: Peter Snyder
>             Fix For: v1_0_0_beta1
>
>
> 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)