Document const, inline, volatile checks semantics
This commit is contained in:
parent
86ce902bf6
commit
c2e0802100
@ -1,2 +1,8 @@
|
||||
// const
|
||||
|
||||
/* This check is unusual in that for a positive answer (the compiler supports
|
||||
const) we undefine const to allow the compiler to recognize it as a keyword
|
||||
and for a negative answer we define it to nothing so that const is
|
||||
effectively removed from the user code. */
|
||||
|
||||
#undef const
|
||||
|
@ -1,2 +1,8 @@
|
||||
// inline
|
||||
|
||||
/* This check is unusual in that for a positive answer (the compiler supports
|
||||
inline) we undefine inline to allow the compiler to recognize it as a
|
||||
keyword and for a negative answer we define it to nothing so that inline is
|
||||
effectively removed from the user code. */
|
||||
|
||||
#undef inline
|
||||
|
@ -1,2 +1,8 @@
|
||||
// volatile
|
||||
|
||||
/* This check is unusual in that for a positive answer (the compiler supports
|
||||
volatile) we undefine volatile to allow the compiler to recognize it as a
|
||||
keyword and for a negative answer we define it to nothing so that volatile
|
||||
is effectively removed from the user code. */
|
||||
|
||||
#undef volatile
|
||||
|
Loading…
Reference in New Issue
Block a user