https://devzone.nordicsemi.com/f/nordic-q-a/16796/app_error_check-usage-patternHello, while reading some nrf5 examples, I&#39;ve stumbled over a pattern in the examples, where the result code of a function is stored in variable (most of the time named err_code ) and then this variable is passed to APP_ERROR_CHECK . Intuitivly, I woulden-USTelligent Community 13Sat, 01 Oct 2016 14:37:44 GMThttps://devzone.nordicsemi.com/thread/64272?ContentTypeID=1Sat, 01 Oct 2016 14:37:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1e1c9616-2553-48fd-aa87-5477d9eb26eaTorsten Robitzki<p>Thanks! :-)</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/64271?ContentTypeID=1Sat, 01 Oct 2016 12:19:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b0425ec6-e6d1-4636-a69a-3c96bb514277RK<p>Doesn&#39;t matter a damn, do whichever you like. However if you are debugging/single-stepping the code it&#39;s easier to have it on two lines so you can see the value of the variable before you enter the APP_ERR_CHECK() and go to the fault handler.</p> <p>In release code it&#39;s all optimized anyway so either piece of code ends up looking exactly the same.</p> <p>Use whichever suits your own personal style, I usually do it all on one line, unless that makes the line incredibly long, in which case I split it up.</p><div style="clear:both;"></div>