Re: [AD] small typo in bmp.c |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I know it would make no effect at all
but i'm used to declare variables as they are supposed to work
----- Original Message -----
From: "George Foot" <gfoot@xxxxxxxxxx>
To: "Javier Gonz?lez" <xaviergonz@xxxxxxxxxx>
Cc: "Allegro Conductors" <conductors@xxxxxxxxxx>
Sent: Sunday, February 04, 2001 9:50 PM
Subject: Re: [AD] small typo in bmp.c
> On Sun, Feb 04, 2001 at 12:43:27AM +0100, Javier Gonz?lez wrote:
> > i've seen that he's right
> > the functions thinks it's 2 bytes
> > (example
> > fileheader->bfType = pack_igetw(f);
> > or
> > pack_iputw(0x4D42, f); /* bfType ("BM") */
> > )
> > so i think he's right :)
>
> Maybe in terms of the actual layout in disk files, but if you
> shorten that field in Allegro it will make no difference to the
> size of the structure (it'll be followed by two bytes of
> padding), and if it's always sent to/from disk using pack_iputw
> and pack_igetw, it will have no effect on the functionality
> either. It will only have effect if the struct is read from
> disk or written to disk as a single block of data.
>
> George
>
> --
> Random project update:
> 22/06/2000: AllegroGL documentation: http://allegrogl.sourceforge.net/
> See under `Documentation' for the AllegroGL Reference Manual in
> various formats.
>
>