[riot-notifications] [RIOT] core: RIOT's own assert macro (#3722)

Oleg Hahm notifications at github.com
Wed Sep 2 12:42:08 CEST 2015


@daniel-k, it seems we're having a different discussion here. An assert is not meant to go into any production environment code. That's just not the purpose of an assert.

For your points: There are errors that you may expect at runtime. These must be handled accordingly in a production environment. And then there are unexpected errors that may always happen (software/hardware bugs, mechanical problems etc.) On an embedded system that runs typically without any user interaction, you can *never* catch and handle all these errors due to memory constraints and in many, many cases the only thing one can do is to bring the system in a defined state again which means resetting the device in 99% of the cases.

---
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/3722#issuecomment-137023823
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20150902/4d1a22c0/attachment.html>


More information about the notifications mailing list