Unsigned char - Revision history

Foxtrot at 11:30, 31 July 2023

2023-07-31T11:30:07Z

Foxtrot at 11:29, 31 July 2023

2023-07-31T11:29:52Z

VolodyA! V Anarhist: released

2015-05-13T07:04:11Z

released

VolodyA! V Anarhist at 12:47, 12 May 2015

2015-05-12T12:47:54Z

VolodyA! V Anarhist: Created page with "{{FormatInfo | name = unsigned char | formattype = electronic | subcat = Data types | subcat2 = C++ data types | subcat3 = | subcat4 ..."

2015-05-11T05:10:03Z

Created page with "{{FormatInfo | name = unsigned char | formattype = electronic | subcat = Data types | subcat2 = C++ data types | subcat3 = | subcat4 ..."

New page

{{FormatInfo
| name = unsigned char
| formattype = electronic
| subcat = Data types
| subcat2 = C++ data types
| subcat3 =
| subcat4 =
| subcat5 =
| thiscat =
| extensions =
| mimetypes =
| locfdd =
| fourccs =
| pronom =
| type code =
| uniform type =
| conforms to =
| released =
| image =
| caption =
}}
{{DISPLAYTITLE:unsigned char}}

'''signed char''' is the smallest unsigned integer type in C++, it often gets typedef-ed as "byte" (alternatively people use [[signed char]] for that reason) because it uses one byte of memory (depending upon what architecture defines it as, but no less than 8 bits). The range of values that can definitely be stored in this type is 0 – 255.

{| class='wikitable'
! 7 !! 6 !! 5 !! 4 !! 3 !! 2 !! 1 !! 0 !! value
|-
| 1 || 0 || 0 || 0 || 0 || 0 || 0 || 0 || 128
|-
| 0 || 1 || 1 || 1 || 1 || 1 || 1 || 1 || 127
|-
| 0 || 0 || 0 || 0 || 0 || 0 || 0 || 0 || 0
|-
| 1 || 1 || 1 || 1 || 1 || 1 || 1 || 1 || 255
|}

Operation 255+1 will likely cause a "roll over" and the result will be 0, but it is unwise to count on that when writing multi-architecture code, as it is possible to define byte in a processor to be more than 8 bits.

==Relationship with char==
'''unsigned char''' uses exact same amount of memory as '''char''', the main difference happens during the output; '''char''' gets interpreted as the code of [[ASCII]] character, while '''unsigned char''' is interpreted as non-negative binary integer.

==Other C++ datatypes of the same size==
* [[char (C++)|char]]
* [[signed char]]

==Other C++ data types storing unsigned integers==
* [[unsigned short int|unsigned short]] no less than 16 bits, no less than char
* [[unsigned int|unsigned (int)]] no less than 16 bits, no less than short
* [[unsigned long int|unsigned long]] no less than 32 bits, no less than int
* [[unsigned long long int|unsigned long long]] no less than 64 bits, no less than long

[[Category:Integer data types]]
[[Category:Enumerable data types]]

@@ Line 21: / Line 21: @@
 }}
 {{DISPLAYTITLE:unsigned char}}
 '''unsigned char''' is the smallest unsigned integer type in C++, it often gets typedef-ed as "byte" (alternatively people use [[signed char]] for that reason) because it uses one byte of memory (depending upon what architecture defines it as, but no less than 8 bits). The range of values that can definitely be stored in this type is 0 &ndash; 255.

@@ Line 22: / Line 22: @@
 {{DISPLAYTITLE:unsigned char}}
-'''signed char''' is the smallest unsigned integer type in C++, it often gets typedef-ed as "byte" (alternatively people use [[signed char]] for that reason) because it uses one byte of memory (depending upon what architecture defines it as, but no less than 8 bits). The range of values that can definitely be stored in this type is 0 &ndash; 255.
+'''unsigned char''' is the smallest unsigned integer type in C++, it often gets typedef-ed as "byte" (alternatively people use [[signed char]] for that reason) because it uses one byte of memory (depending upon what architecture defines it as, but no less than 8 bits). The range of values that can definitely be stored in this type is 0 &ndash; 255.
 {| class='wikitable'

← Older revision		Revision as of 12:47, 12 May 2015
Line 37:		Line 37:

	Operation 255+1 will likely cause a "roll over" and the result will be 0, but it is unwise to count on that when writing multi-architecture code, as it is possible to define byte in a processor to be more than 8 bits.		Operation 255+1 will likely cause a "roll over" and the result will be 0, but it is unwise to count on that when writing multi-architecture code, as it is possible to define byte in a processor to be more than 8 bits.
−
−	~~==Relationship with char==~~
−	'''unsigned char''' uses exact same amount of memory as '''char''', the main difference happens during the output; '''char''' gets interpreted as the code of [[ASCII]] character, while '''unsigned char''' is interpreted as non-negative binary integer.

	==Other C++ datatypes of the same size==		==Other C++ datatypes of the same size==

@@ Line 16: / Line 16: @@
 | uniform type   =
 | conforms to    =
-| released       =
+| released       = 1983
 | image          =
 | caption        =