#precompiler

[quanrel]

Interbase 5.6 C & C++ Pre-Compiler - Buy on Amazon

[goodanswerbiz]

How-to: Why #define TRUE (1==1) in a C boolean macro instead of simply as 1? #it #programming #dev

How-to: Why #define TRUE (1==1) in a C boolean macro instead of simply as 1? #it #programming #dev

Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

I’ve seen definitions in C

#define TRUE (1==1) #define FALSE (!TRUE)

Is this necessary? What’s the benefit over simply defining TRUE as 1, and FALSE as 0?

Answer [by SLaks]: Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

This approach will use the actual boolean type (and resolve to true and false) if…

View On WordPress

[sevennet-blog]

How to: Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

How to: Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

I’ve seen definitions in C

#define TRUE (1==1) #define FALSE (!TRUE)

Is this necessary? What’s the benefit over simply defining TRUE as 1, and FALSE as 0?

Answer: Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

This approach will use the actual boolean type (and resolve to true and false) if the compiler…

View On WordPress