generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Define convenient FATAL_ERROR() and FATAL_ERROR_IF() macros

Browse Source 
R=henrike@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/16079004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@6701 4adac7df-926f-26a2-2b94-8c16560cd09d
This commit is contained in:
kwiberg@webrtc.org 2014-07-16 08:34:58 +00:00
parent e8ea33ccb1
commit 0fa6366ed1
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
webrtc/base/checks.h
View File

@ -21,8 +21,17 @@ void Fatal(const char* file, int line, const char* format, ...);
} // namespace rtc
// Trigger a fatal error (which aborts the process and prints an error
// message). FATAL_ERROR_IF may seem a lot like assert, but there's a crucial
// difference: it's always "on". This means that it can be used to check for
// regular errors that could actually happen, not just programming errors that
// supposedly can't happen---but triggering a fatal error will kill the process
// in an ugly way, so it's not suitable for catching errors that might happen
// in production.
#define FATAL_ERROR(msg) do { rtc::Fatal(__FILE__, __LINE__, msg); } while (0)
#define FATAL_ERROR_IF(x) do { if (x) FATAL_ERROR("check failed"); } while (0)
// The UNREACHABLE macro is very useful during development.
#define UNREACHABLE() \
rtc::Fatal(__FILE__, __LINE__, "unreachable code")
#define UNREACHABLE() FATAL_ERROR("unreachable code")
#endif // WEBRTC_BASE_CHECKS_H_