From: cheekai AT gen DOT co DOT jp (Chin Chee-Kai)
Subject: one point (Was [Re: FW: Re: wxwin port])
16 Nov 1996 22:07:53 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <Pine.3.07.9611171350.A22425-a100000.cygnus.gnu-win32@sumimasen.gen.co.jp>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: gensstc.gen.co.jp: smap set sender to <cheekai AT gen DOT co DOT jp> using -f
Original-To: Keith Gary Boyce <garp AT opustel DOT com>
Original-Cc: gnu-win32 AT cygnus DOT com
In-Reply-To: <199611102333.6951.0@dsbc.icl.co.uk>
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hmm, a minor point -- the "16 bytes" effect doesn't seem to be
"from gnu-win32".  I run into this same situation writing BMP
processing functions earlier on using gcc (2.7.2) on both
Sun Sparc & SGI Indy.  

A "sizeof(BITMAPFILEHEADER)" generated 16 using Sun's cc,
SGI's cc, and gcc on both platforms as well.  In the end,
I resorted to #define-ing 14 on a character array to suit
my purposes.


Chin Chee-Kai (Last, First)
Internet Email-ID:	cheekai AT gen DOT co DOT jp
Gen Tech Corporation


On Sun, 10 Nov 1996, J.J.Farrell wrote:

> > From: Keith Gary Boyce <garp AT opustel DOT com>
> > 
> > Does anyone have any input on why 16 bytes from gnu-win32 and
> > 14 for other compiler
> > 
> > >typedef struct tagBITMAPFILEHEADER {
> > >        WORD    bfType;
> > >        DWORD   bfSize;
> > >        WORD    bfReserved1;
> > >        WORD    bfReserved2;
> > >        DWORD   bfOffBits;
> > >} BITMAPFILEHEADER, FAR *LPBITMAPFILEHEADER, *PBITMAPFILEHEADER;

[[ ... other quotations deleted ... ]]

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".