Do you

Do you
#include

or
#define TRUE 1
#define FALSE 0
typedef int bool;

or just let it be and use 0 and 1 and ints directly?

I stop being retarded, m9

Explain

I don't teach pajeets

typedef enum {true, false} bool;

or plain unsigned chars or ints.. unless you need to serialize and/or size matters. Allows you to have more states if you like.

Neither, I use c99 because I can

So?

You #include

both are wrong you faggot

>typedef int bool
>int
Disgusting.

#include

char is slower

>c
>2016

sure if it makes you feel smarter having to re-implement true or false in every project

I use Rust

neither

typedef enum {false = 0, true = 1} boolean;

...

contestant 1

just use ints and return 1 for true, 0 for false
If you're stupid enough to use C, there's no point in trying to act smart about it.

conestant 4

2?

2

contestant 2 cause it points to [0]

Undefined behavior

Friendly reminder to always
#define TRUE FALSE

2

Black boy, white girl.

2 because she's obviously a coal burner

>or just let it be and use 0 and 1 and ints directly?
this. technically zero and nonzero, not zero and one. less verbose and anyone smart enough to read or write C understands it.

And that's why C sucks, kids.