BYTE, char data corruption

**Ancient Dragon** · 11-12-2005

Originally Posted by dwks

It does work?

Oh, you mean doesn't. It does work, because all I want copied is the address.

That was a typo that I later corrected.

If all you want is the address, then great, it will work for you.

**dwks** · 11-12-2005

You are one of a very select few who do. I've never see that before in over 20 years.

It's the only way to initialize (as Thantos says) a struct. It's the same as with arrays. Do you never do that either?

This code sets all elements to zero:

Code:

int x[10] = {0};

**dwks** · 11-12-2005

If all you want is the address, then great, it will work for you.

The address is what I would expect, since it's a pointer.

**Ancient Dragon** · 11-12-2005

Originally Posted by dwks

It's the only way to initialize (as Thantos says) a struct. It's the same as with arrays. Do you never do that either?

No. Never like that, except maybe in an array of structures when initializers contain no function calls.

Originally Posted by dwks

This code sets all elements to zero:

Code:

int x[10] = {0};

Do that all the time, but that's not the same as initializing a structure.

**dwks** · 11-12-2005

but that's not the same as initializing a structure.

It's pretty much the same. They both initialize things. The only difference is that with structures, the type you're initializing can change.

**Denethor2000** · 11-12-2005

Originally Posted by Thantos

A BYTE is nothing more then a fancy unsigned char.

In C++ language, yes. I use BYTE because it's what I'm actually dealing with: bytes. Less confusing to me, and whoever I share my code with.

how does it corrupt it?

Changing it to a char makes 50% of my bytes turn from 0x0000008E to 0xFFFFFF8E.

**dwks** · 11-12-2005

Use & then to elininate the extra Fs.

[edit]

Changing it to a char

How? With a cast?[/edit]

**Ancient Dragon** · 11-12-2005

Originally Posted by Denethor2000

Changing it to a char makes 50% of my bytes turn from 0x0000008E to 0xFFFFFF8E.

Impossible -- one byte cannot contain that big a number. The max falue of a byte is 0xff. you are probably seeing the output of a debugger, which is not necessarily the same as what is actually stored in the memory location.

**Thantos** · 11-12-2005

In C++ language, yes. I use BYTE because it's what I'm actually dealing with: bytes. Less confusing to me, and whoever I share my code with

Obviously its causing more problems then its helping.

However you still haven't given up all the information. Or hell even a full code example. if all you need to do is write it out to a file use write() on a binary file

**dwks** · 11-12-2005

Perhaps he should be "changing" it to an unsigned char.

**Thantos** · 11-12-2005

Impossible -- one byte cannot contain that big a number. The max falue of a byte is 0xff.

What if you were dealing with 16 bit bytes? 32 bit bytes? They'd have a high value then that.

BTW I'm guessing we all are assuming you are using the BYTE specified in the windows header. Can someone tell me if its a #define or typedef?

**Ancient Dragon** · 11-12-2005

Originally Posted by Thantos

What if you were dealing with 16 bit bytes? 32 bit bytes? They'd have a high value then that.

BTW I'm guessing we all are assuming you are using the BYTE specified in the windows header. Can someone tell me if its a #define or typedef?

You have a point -- but have you ever heard of such an animal? Not to say there isn't one, but I doubt the OP is using it.

Originally Posted by windef.h

typedef unsigned char BYTE;

**Denethor2000** · 11-12-2005

Bytes are 2 bits. Words are 4 bits. Dwords are 8 bits. Qwords are 16 bits.

All bytes are 2bit, 0xFF. Stop asking if my bytes are 32bit or 16bit... They're neither, obviously.

Anyway, using memcpy lets me copy my array into the struct, and it works correctly. Thanks for the help. <3

**Ancient Dragon** · 11-12-2005

Originally Posted by Denethor2000

Bytes are 2 bits. Words are 4 bits. Dwords are 8 bits. Qwords are 16 bits.

All bytes are 2bit, 0xFF. Stop asking if my bytes are 32bit or 16bit... They're neither, obviously.

Anyway, using memcpy lets me copy my array into the struct, and it works correctly. Thanks for the help. <3

No. on MS-Windows and *nix a byte is 8 bits. What you probably mean is a nibble, which is half the size of a byte.

-- If you don't know what a byte is, don't bother reading. --

I guess you should never have started this thread, since you don't know what a byte is either

**Thantos** · 11-12-2005

Ok you are seriously in need of some education then. Bytes are the lowest addressible memory element. By standard they are required to contain at least 8 bits. So whereever you got your size definations, burn it.