Why is a char and a bool the same size in c++?

by

In modern computer architectures, a byte is the smallest addressable unit of memory. To pack multiple bits into a byte requires applying extra bit-shift operations. At the compiler level, it’s a trade off of memory vs. speed requirements (and in high-performance software, those extra bit-shift operations can add up and slow down the application needlessly).

More Related Contents:

  1. Double Negation in C++
  2. Is sizeof(bool) defined in the C++ language standard?
  3. Alternative to vector
  4. How to create a byte out of 8 bool values (and vice versa)?
  5. Can I assume (bool)true == (int)1 for any C++ compiler?
  6. Does true equal to 1 and false equal to 0? [duplicate]
  7. String literal matches bool overload instead of std::string
  8. C++ printing boolean, what is displayed?
  9. Is C/C++ bool type always guaranteed to be 0 or 1 when typecast’ed to int?
  10. Why is a boolean 1 byte and not 1 bit of size?
  11. What is the printf format specifier for bool?
  12. C++ : why bool is 8 bits long?
  13. Can a bool read/write operation be not atomic on x86? [duplicate]
  14. Is the use of std::vector objects in C++ acceptable, or should I use an alternative?
  15. bool operator ++ and —
  16. Why the sizeof(bool) is not defined to be one, by the Standard itself?
  17. Why is there an implicit type conversion from pointers to bool in C++?
  18. Using bitwise operators for Booleans in C++
  19. Casting int to bool in C/C++
  20. Is !! a safe way to convert to bool in C++?
  21. Is it ok to read a shared boolean flag without locking it when another thread may set it (at most once)?
  22. Converting bool to text in C++
  23. Why use !! when converting int to bool?
  24. Setting extra bits in a bool makes it true and false at the same time
  25. C++ bool returns 0 1 instead of true false
  26. How is a bool represented in memory?
  27. Why is a C++ bool var true by default?
  28. Why use iterators instead of array indices?
  29. C++ Undefined Reference to vtable and inheritance
  30. Weird MSC 8.0 error: “The value of ESP was not properly saved across a function call…”

Leave a Comment