search

PelionIoT / mbed-trace

mbed trace library
Apache License 2.0
18 stars 15 forks source link

README is a bit confusing about trace-level order #56

Closed teetak01 closed 7 years ago

teetak01 commented 7 years ago

Info level is mentioned in documentation as step above cmd_printf, even through it should be the second highest.

ciarmcom commented 7 years ago

ARM Internal Ref: IOTSYST-1874

jupe commented 7 years ago

it's actually kind of correct, maybe little confusion way documented. When tracing with level TRACE_LEVEL_CMD it behaviour little differently when it is printed out, it uses cmd_printf function pointer which can be define by mbed_trace_cmdprint_function_set() -function. This level should not be used in normal case, there was special use case for it in first place.

jupe commented 7 years ago

Is there something else what you would like to know ?

teetak01 commented 7 years ago

I mean the order they are mentioned is wrong:

    debug
    warning
    error
    info
    cmdline (special behavior, should not be used)

Should be:

    debug
    info
    warning
    error
    cmdline (special behavior, should not be used)
jupe commented 7 years ago

aa, sorry, I little misunderstand :). Could you create fix PR for doc ? ;)

tommikas commented 7 years ago

Fixed in #57.