45

In VC++ we have the data type “BOOL” which can assume the value TRUE or FALSE, and we have the data type “bool”, which can assume the value true or false.

What is the difference between them and when should each data type be used?

Gordon Brandly
  • 352
  • 4
  • 15
Umesha MS
  • 2,861
  • 8
  • 41
  • 60

3 Answers3

51

bool is a built-in C++ type while BOOL is a Microsoft specific type that is defined as an int. You can find it in windef.h:

typedef int                 BOOL;

#ifndef FALSE
#define FALSE               0
#endif

#ifndef TRUE
#define TRUE                1
#endif

The values for a bool are true and false, whereas for BOOL you can use any int value, though TRUE and FALSE macros are defined in the windef.h header.

This means that the sizeof operator will yield 1 for bool (the standard states, though, that the size of bool is implementation defined), and 4 for BOOL.

Source: Codeguru article

luvieere
  • 37,065
  • 18
  • 127
  • 179
  • 8
    sizeof(BOOL) is still 4 on a 64-bit Windows machine. Isolating itself from the compiler type implementations is the reason these typedefs exist. – Hans Passant Jun 21 '11 at 05:10
  • 1
    @Hans Removed the 64-bit reference. – luvieere Jun 21 '11 at 06:13
  • 7
    WARNING: sizeof(bool) is not specified in microsoft c++ and changed from 4 bytes to 1 byte between c++ 4.2 and 5.0 (see http://msdn.microsoft.com/en-US/en-use/library/tf4dy80a.aspx) – eFloh Apr 16 '14 at 07:32
16

Windows API had this type before bool was thrown into C++. And that's why it still exits in all Windows function that take BOOL. C doesn't support bool data-type, therefore BOOL has to stay.

Ajay
  • 18,086
  • 12
  • 59
  • 105
15

To add to what luvieere has said, you can return something other than TRUE or FALSE from a function returning a BOOL e.g.,

BOOL myFunc(int a)
{
    if (a < 3) return FALSE;
    else if (a > 3) return TRUE;
    else return 2;
}

And this is possible because a BOOL is essentially an int.

Please note that this is not advisable as it severely destroys the general readability of code but it is something you can come across and you will be wondering why it is so.

Aamir
  • 14,882
  • 6
  • 45
  • 69
  • 12
    +1 for pointing out that this is a really bad idea. The whole reason to use BOOL is to restrict the values to TRUE/FALSE; if you want `int` you should use `int`. – Mark Ransom Jun 21 '11 at 15:22
  • 1
    Many (but not all) Windows API functions treat any non-zero `BOOL` as `TRUE`. Because this behaviour is not consistent, you should always explicitly use `TRUE` (i.e. `1`) and not non-zero. This can be tricky because [some languages](https://stackoverflow.com/a/14462348/1836776) define `True` as all bits set (`-1` for signed integers) – Marc Durdin Aug 20 '20 at 00:07