Thread: Struct size incorrect

I've created the following struct...

Code:

typedef struct {
	short 	type;
	int 	fileSize;
	short 	res0;
	short 	res1;
	int 	dataOffset;
} BMPFILEHEADER;

By my calculations, it should equal 14 bytes. Two bytes for each short and four bytes for each int. The thing is, if I do sizeof(BMPFILEHEADER) it equals 16 and I have no clue why. Especially when if I do sizeof(int) and sizeof(short) they come out at four bytes and two bytes respectively

I'm using gcc in Cygwin as my compiler, if that makes a difference. I'm downloading the express edition of Visual C++ 2008 as I write this to see if that makes a difference.

Any ideas?

Ah, right. I seem to remember reading something about this a while ago. Isn't there some kind of pragma directive I can add to stop it from doing this?

You usually don't want to do that since it optimizes for the processor to access data.
Otherwise look in your compiler's settings, because it's different for each compiler.

hehe, i just came here to ask absolutely the same question...
I have a structure (a string of 50 bytes, a double of 4 bytes and an int of 4 bytes)...

Code:

typedef struct product {
	char name[50];
	float price;
	int quantity;
};

I kept getting 60 bytes when i checked its size instead of 58. Now i know why...

P.S. sorry to hijack your thread redneon, but what if i wanted to read the second piece of the structure (i.e. price), what should the offset be?

[name][padding][price][padding][quantity]
__50__+___1___+__4__+___1___+___4___ = 60 bytes

Depends on the padding. Again, to be safe, just let the compiler do its work. Access the member by its name, and it will work fine.

Code:

struct product prod;
prod.price = 1.50;

Sorry, i shoudl've been clearer... If I had written the structure into a file and then wanted to access only the price (to edit it for example)... Would I use something of this sort?

Code:

fseek(file_pointer, sizeof(product.name) + 1, SEEK_SET)

Once again, depends on padding. You can do trial & error, but the safest way is to write the entire struct and read the entire struct from the file, unchanged. This also takes into account that you did not change padding settings and that you did not change endianness - ie trying to read an existing file on another platform.
I'm not sure how much or where the padding is, but you could find it by doing like this:

Code:

struct product prod;
int off = &prod.price - ∏ // Calculate offset of price inside the struct of prod.

Oh, thanks for clearing that up...
btw, Elysia, I have this function to add a new product:

Code:

void add_product(product *p) {
	printf("Enter product description : ");
	gets(p->name);
	printf("Enter price per unit (cent) : ");
	scanf("%f", &p->price);
	printf("Enter stock level: ");
	scanf("%d", &p->quantity);
}

if I wanted to modify just the price, would the following function work? (Thats assuming I moved the offset to the start of the product structure)...

Code:

void edit_price(product *p) {
	printf("Enter price per unit (cent) : ");
	scanf("%f", &p->price);
}

The code is pretty much the same apart the left out name and quantity parts...

Yes, it would work, even if you don't move the price to start of the structure.
Why? Because it reads the address of &price, and not the address of the structure start.

Cheers... I've been struggling with this problem all weekend... Will now try and put the theory in practice

Good luck.

I know for a fact that the Mingw port of GCC, and GCC support the following format:

Code:

struct foobar {

     int yo;

     char homie;

}__attribute__ ((packed));