What is your preferred logical pair: 1/0 Yes / No True / False?

Question

• When working with MySQL, I usually use the BOOLEAN type, which is equivalent to TINYINT (1) or 1/0
• Most languages ​​I work with are preferable to true / false.
• When displaying forms, sometimes "Yes / No" makes sense

Answer 1

enum Bool { True, False, FileNotFound }; 

http://thedailywtf.com/Articles/What_Is_Truth_0x3f_.aspx

Answer 2

In the code: true / false.

In the user interface: Yes / No or OK / Cancel

Answer 3

true and false make much more sense to me, in the code - partly due to my acquaintance, I'm sure. I suspect I'm used to yes and no pretty quickly. 1 and 0 really don't work for me though.

Consider the expression

 age == 5 

This is a test for truth. Is the value of age 5? Yes it's true. Both "yes" and "no" would be good for me, but the idea is that the answer to the question "Is the value of age 5?" "1" seems pretty intuitive to me. Just because a typical binary representation of the truth does not mean that it is useful for higher abstraction.

Answer 4

Which is easier to read?

 while(true) {} while(yes) {} while(1) {} 

In most cases, I adhere to the rights.

Answer 5

Here are the rules that I live ...

Rule number 1

Use well-defined constants in the programming languages ​​that you use to communicate with the CPU, i.e. true / false in most modern cases for boolean values. If the database offers a boolean type or some such equivalent, of course, it should be used.

Rule number 2

Interaction with users of your software using their preferred language and idiom, that is, Yes / No questions that should be asked by Yes / No (or, possibly, an alternative to No, for example Cancel).

Rule number 3

Uncertainty must be expressed in terms of volume, i.e. “it depends”, followed by the question “about what?”. I know developers who answer the question by copying and pasting almost every dependency they may need in every project code file, like the using statement. This is just careless, and please take care of the alphabetical, or at least the group namespace together.

When bool Just Is Not Enough

By the way, the interesting twist on this available in C # is Nullable;

You can write

 Nullable<bool> RespondToIritatingQuestion() { return new Nullable<bool>(); } 

OR

 bool? RespondToIritatingQuestionWithSytle() { return new bool?(); } 

and the questionnaire will have to evaluate your answer before even knowing what answer, if any, maybe ...

 bool? answer = RespondToIritatingQuestionWithStyle(); if (answer.HasValue) Trace.WriteLine("The bloke responded with " + answer.Value.ToString()); else Trace.WriteLine("The bloke responded with 'depends'."); 

Answer 6

1 or 0 for SQL. SQL has a boolean type for some reason. In addition, in very large databases, this can affect performance.

Answer 7

I use booleans for true / false fields in databases. Some people use ENUM('true', 'false') , but that is not my preference. For programming languages, I always use true / false, even if setting 0 or 1 will work. And if the form requires yes / no, I still use booleans to represent the values, but display them as strings that are more logical.