Elysian Shadows

davidthefat wrote:So exactly what is a byte? IDK how to ask this, but is it a hex? or binary? or what? When the arguement takes in a byte, WTF can I put into there? Im asking for Java, and C++. My server is programmed in Java (its a robot, and it uses java...) and the client is in C++, so will it have problems when sending and receiving a socket with ints or floats and doubles? They don't have the same "standards" from what I know, or is it just better to send a giant string? I am trying to transfer an array of doubles to the PC from the robot through sockets. IDK if I should send the values one by one and check if they are the same and then send the other one or not check at all?

I am trying to render a 3d image captured from the robot on the client PC's screen using OpenGL and SDL. I got the getting the image part down, and the drawing part, but not the communication, which is one vital factor that can render this useless.

avansc wrote: a byte is just a word that means 8 sequential bits. the byte int binary 1111 1111 is FF in hex and 255 in decimal (unsigned of course.)
a nibble is half a byte, so 4 bits.

davidthefat wrote:

avansc wrote: a byte is just a word that means 8 sequential bits. the byte int binary 1111 1111 is FF in hex and 255 in decimal (unsigned of course.)
a nibble is half a byte, so 4 bits.

Thanks I can always rely on you, so I can just send raw Binary or Hex though it?

short wrote:

davidthefat wrote:

avansc wrote: a byte is just a word that means 8 sequential bits. the byte int binary 1111 1111 is FF in hex and 255 in decimal (unsigned of course.)
a nibble is half a byte, so 4 bits.

Thanks I can always rely on you, so I can just send raw Binary or Hex though it?

You can't send raw binary or hex through it, binary and hex are just a way of viewing the data.. You can send bytes though. Open up your calculator and you can see this, a number can be viewed in base 2 (binary) base 10 (decimal) or base 16 (hexadecimal) however the data, no matter how your viewing it, is the same. recap: you send bytes, you can view those bytes in binary, hex, whatever.

davidthefat wrote:

avansc wrote: a byte is just a word that means 8 sequential bits. the byte int binary 1111 1111 is FF in hex and 255 in decimal (unsigned of course.)
a nibble is half a byte, so 4 bits.

Thanks I can always rely on you, so I can just send raw Binary or Hex though it?

avansc wrote: a byte is just a word that means 8 sequential bits.

K-Bal wrote:

avansc wrote: a byte is just a word that means 8 sequential bits.

The standard just tells that a byte is the smallest word. It does not tell how much bits it has. Just for completeness

K-Bal wrote:

avansc wrote: a byte is just a word that means 8 sequential bits.

The standard just tells that a byte is the smallest word. It does not tell how much bits it has. Just for completeness

avansc wrote:

K-Bal wrote:

avansc wrote: a byte is just a word that means 8 sequential bits.

The standard just tells that a byte is the smallest word. It does not tell how much bits it has. Just for completeness

Ummm.. wel i might be wrong here, but as far as i know a byte is a byte. It is always 8 bits on any arch.

The byte (pronounced /ˈbaɪt/) is a unit of digital information in computing and telecommunications. It is an ordered collection of bits, in which each bit denotes the binary value of 1 or 0. Historically, a byte was the number of bits (typically 5, 6, 7, 8, 9, or 16) used to encode a single character of text in a computer and it is for this reason the basic addressable element in many computer architectures. The size of a byte is typically hardware dependent, but the modern de facto standard is 8 bits, as this is a convenient power of 2. Most of the numeric values used by many applications are representable in 8 bits and processor designers optimize for this common usage. Signal processing applications tend to operate on larger values and some digital signal processors have 16 or 40 bits as the smallest unit of addressable storage (on such processors a byte may be defined to contain this number of bits). The term octet was explicitly defined to denote a sequence of 8 bits because of the ambiguity associated with the term byte and is widely used in communications protocol specifications.

The C and C++ programming languages, for example, define byte as "addressable unit of data large enough to hold any member of the basic character set of the execution environment" (clause 3.6 of the C standard). The C standard requires that the char integral data type is capable of holding at least 255 different values, and is represented by at least 8 bits (clause 5.2.4.2.1). Various implementations of C and C++ define a byte as 8, 9, 16, 32, or 36 bits. The actual number of bits in a particular implementation is documented as CHAR_BIT as implemented in the limits.h file. Java's primitive byte data type is always defined as consisting of 8 bits and being a signed data type, holding values from −128 to 127.