Message-ID: <32506D04.77F@gbrmpa.gov.au>
Date: Tue, 01 Oct 1996 08:59:48 +0800
From: Leath Muller <leathm AT gbrmpa DOT gov DOT au>
Reply-To: leathm AT gbrmpa DOT gov DOT au
Organization: Great Barrier Reef Marine Park Authority
MIME-Version: 1.0
To: John Panettiere <jmarco AT cnct DOT com>
CC: djgpp AT delorie DOT com
Subject: Re: packed data structures?
References: <52nl1a$kqv AT news2 DOT cnct DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> At first I didn't know why my VBE2 code wasn't working, but then I
> realized that djgpp wasn't packing the data structures - so I browsed
> the info files and found "__attribute__((packed))", which seemed to be
> the answer I was looking for.  I applied this attribute to every field
> in all of my VBE2 data structures, but the problem still seemed to
> remain - 16 bit fields were being padded!  Is there a known problem
> with packing, or is there something I'm overlooking?

Are you sure you have defined the structures correctly? I do this
exactly as you have stated, and have no problem at all with it. How
are you defining your 16 bit fields? You should be using short int's...
:) 
 
> I've already downloaded the vbe2 sample code that is mentioned in the
> faq, in fact its what my code is largely based on.  The author of that
> code doesn't go through the entire list of videomodes using the
> "VideoModePtr" field returned in the VbeInfoBlock structure; this is
> something I need to do and is at the heart of my present predicament.

I'm confused. :)  Are you:
i)	asking how to go through all the video modes; or
ii)	saying that the non-packing of your structure effects the looking
	up of all video modes?

If you need help, mail me... :)

Leathal.