10363 2016-10-03 22:20:01 +0000 Suggested note to clarify that bb.fatal() raises an exception 2016-10-04 16:23:39 +0000 1 1 9 Documentation Reference handbook 2.2 x86 Multiple RESOLVED FIXED 04 Oct 2016: RESOLVED Undecided normal 2.2 M4 1 ulfalizer srifenbark poky.doc.watcher poky.watcher richard.purdie --- --- Done (doc changes complete) oldest_to_newest 66845 0 ulfalizer 2016-10-03 22:20:01 +0000 Hello, It might be unclear that bb.fatal() throws an exception, making people put 'return' after it. Adding this note after the bb.fatal() description in '2.3.11. Recipe Logging Mechanisms' could help: Note { bb.fatal() throws an exception, meaning you do not need to put a 'return' statement after it. } Exactly which exception it is (BBHandledException) might be an implementation detail, so maybe it should be left out. Cheers, Ulf 66846 1 ulfalizer 2016-10-03 22:22:13 +0000 Self-nit: "Raises an exception" is the standard Python terminology. 66847 2 ulfalizer 2016-10-03 22:36:28 +0000 Feel free to close right away without review for tiny stuff like this btw, even if you make small edits. I could always reopen it if I see an error. :) Cheers, Ulf 66856 3 richard.purdie 2016-10-04 09:48:23 +0000 I did worry when I saw the title of this bug, I think exactly what happens behind the scenes with bb.fatal is an implementation detail and could well change but I think you've made that clear. 66872 4 srifenbark 2016-10-04 16:23:39 +0000 Ulf, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#recipe-logging-mechanisms for the new note. Setting to RESOLVED and putting the doc flag to "done." Scott