Redefine gdb_static_assert as static_assert
Since we use C++11, we can use static_assert instead doing the trick that makes a negative-sized array if the expression is false. static_assert is built in the language and gives clearer error messages. To avoid modifying the usages of gdb_static_assert, redefine gdb_static_assert in terms of static_assert, passing an empty message. If we want to add an assert with a message, it's always possible to use static_assert directly. gdb/ChangeLog: * common/gdb_assert.h (gdb_static_assert): Redefine using static_assert.
This commit is contained in:
parent
798a7429f9
commit
ed9376bd95
2 changed files with 6 additions and 2 deletions
|
@ -22,8 +22,7 @@
|
|||
/* A static assertion. This will cause a compile-time error if EXPR,
|
||||
which must be a compile-time constant, is false. */
|
||||
|
||||
#define gdb_static_assert(expr) \
|
||||
extern int never_defined_just_used_for_checking[(expr) ? 1 : -1]
|
||||
#define gdb_static_assert(expr) static_assert (expr, "")
|
||||
|
||||
/* PRAGMATICS: "gdb_assert.h":gdb_assert() is a lower case (rather
|
||||
than upper case) macro since that provides the closest fit to the
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue