On 11/13/2012 04:13 PM, danielfsan...@att.net wrote:
> +#define __compiletime_assert(condition, msg, __func) \
> + do {\
> + bool __cond = !(condition); \
> + extern
On 11/13/2012 04:13 PM, danielfsan...@att.net wrote:
+#define __compiletime_assert(condition, msg, __func) \
+ do {\
+ bool __cond = !(condition); \
+ extern void
On Tue, Nov 13, 2012 at 04:13:41PM -0600, danielfsan...@att.net wrote:
> Introduce compiletime_assert to compiler.h, which moves the details of
> how to break a build and emit an error message for a specific compiler
> to the headers where these details should be. Following the tradition of
> the
On Tue, Nov 13, 2012 at 04:13:41PM -0600, danielfsan...@att.net wrote:
Introduce compiletime_assert to compiler.h, which moves the details of
how to break a build and emit an error message for a specific compiler
to the headers where these details should be. Following the tradition of
the
Introduce compiletime_assert to compiler.h, which moves the details of
how to break a build and emit an error message for a specific compiler
to the headers where these details should be. Following the tradition of
the POSIX assert macro, compiletime_assert creates a build-time error
when the
Introduce compiletime_assert to compiler.h, which moves the details of
how to break a build and emit an error message for a specific compiler
to the headers where these details should be. Following the tradition of
the POSIX assert macro, compiletime_assert creates a build-time error
when the
6 matches
Mail list logo
