Is there a integer data type of one byte in gcc?

[Ptp]

is there a integer data type of one byte in gcc?
I know delphi have fundamental integer types include byte, shortint...
the byte types is unsigned 8-bit, such as below:

procedure TForm1.Button1C lick(Sender: TObject);
var
onebyte: byte;
^^^^

¡° ¨Ó·½:¡E¨}¬ü®a±Ú Á`¹ë hiperfect.com¡E[FROM: localhost]

[Joona I Palaste]

Ptp <pt*****@hiperf ect.com> scribbled the following:

is there a integer data type of one byte in gcc?

char.

--
/-- Joona Palaste (pa*****@cc.hel sinki.fi) ------------- Finland --------\
\-- http://www.helsinki.fi/~palaste --------------------- rules! --------/
"To err is human. To really louse things up takes a computer."
- Anon

[Andreas Kahari]

In article <48********@hip erfect.com>, Ptp wrote:

is there a integer data type of one byte in gcc?
I know delphi have fundamental integer types include byte, shortint...
the byte types is unsigned 8-bit, such as below:

procedure TForm1.Button1C lick(Sender: TObject);
var
onebyte: byte;
^^^^

I don't know about gcc, but standard C has the char type, which
is one byte by definition. One byte is CHAR_BIT bits (in
<limits.h>), usually 8.
--
Andreas Kähäri

[Grumble]

>> Is there an integer data type of one byte in gcc?

char.

I think he meant 8 bits.

Is uint8_t guaranteed to be 8 bits wide on every platform?

[Dan Pop]

In <48********@hip erfect.com> pt*****@hiperfe ct.com (Ptp) writes:

is there a integer data type of one byte in gcc?

Not one, but three, and not only in gcc but in any conforming C compiler:
char, signed char, unsigned char.

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Joona I Palaste]

Grumble <in*****@kma.eu .org> scribbled the following:

Is there an integer data type of one byte in gcc?
char.

I think he meant 8 bits.
char is guaranteed to be at least 8 bits wide on every platform. If the
OP wants a type that is exactly 8 bits wide, then I would want to know
why.
Is uint8_t guaranteed to be 8 bits wide on every platform?

I'd figure so, on platforms that support it in the first place.

--
/-- Joona Palaste (pa*****@cc.hel sinki.fi) ------------- Finland --------\
\-- http://www.helsinki.fi/~palaste --------------------- rules! --------/
"Outside of a dog, a book is a man's best friend. Inside a dog, it's too dark
to read anyway."
- Groucho Marx

[pete]

Andreas Kahari wrote:

In article <48********@hip erfect.com>, Ptp wrote:

is there a integer data type of one byte in gcc?
I know delphi have fundamental integer types include byte, shortint...
the byte types is unsigned 8-bit, such as below:

procedure TForm1.Button1C lick(Sender: TObject);
var
onebyte: byte;
^^^^

I don't know about gcc, but standard C has the char type, which
is one byte by definition.

If one were going to use a one byte integer
for mathematical purposes, rather than for string characters,
I would suggest choosing either "signed char" or "unsigned char",
instead of plain "char".

--
pete

[Martin Ambuhl]

Ptp wrote:

is there a integer data type of one byte in gcc?

char, signed char, unsigned char

--
Martin Ambuhl

[August Derleth]

pt*****@hiperfe ct.com (Ptp) wrote in message news:<48******* *@hiperfect.com >...

is there a integer data type of one byte in gcc?

If gcc is a conformant C compiler (and it isn't always), it has three
types guaranteed to be at least eight bits wide: char, unsigned char,
and signed char.

What's the difference between signed and unsigned? One type can hold a
sign and has been modified in an implementation-specified way to do
it, the other cannot hold a sign and has behavior more stringently
defined by the Standard in the various edge cases. One of the edge
cases is wrap-around: If you do

#include <limits.h>

unsigned char foo(void)
{
unsigned char i = UCHAR_MAX;
i++;
return(i);
}

the return value from foo() is defined (it is 0). If, however, you do

#include <limits.h>

signed char bar(void)
{
signed char i = CHAR_MAX;
i++;
return(i);
}

the return value from bar() is implementation-dependent and is allowed
to be a trap representation (that is, one that sends the machine into
a tizzy).

So, if you want to treat your at-least-eight-bits-wide values as an
unsigned type with a strictly defined behavior in case of overflow,
use unsigned char. If you need to hold a sign, use signed char or
char.

[CBFalconer]

Dan Pop wrote:

pt*****@hiperfe ct.com (Ptp) writes:

is there a integer data type of one byte in gcc?

Not one, but three, and not only in gcc but in any conforming C
compiler: char, signed char, unsigned char.

At last a correct answer. However, of the three, using char in
arithmetical expressions is likely to lead to unexpected results.

--
Chuck F (cb********@yah oo.com) (cb********@wor ldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home .att.net> USE worldnet address!