Re: [AD] small typo in bmp.c

[Javier Gonzalez <xaviergonz@xxxxxxxxxx>]

Agreed, could be (*is*) interesting...

----- Original Message -----
From: "Ben Davis" <ben@xxxxxxxxxx>
To: <conductors@xxxxxxxxxx>
Sent: Monday, February 05, 2001 2:35 AM
Subject: RE: [AD] small typo in bmp.c


> > > I wonder if there is an appropriate place in the docs to make this
point
> > > about why ints are faster than shorts. I too used to use shorts
> > all the time
> > > because I was unaware that they were slower.
> >
> > Perhaps we could lump it together with information about why 24 bit
> > is slower than 32 bit, or that sometimes 15/16 bit is also slower
> > than 32 bit.  Kind of that same thing.  Otherwise it's not really
> > appropriate, IMHO.
>
> Maybe we should create a new docs section with programming tips. It would
> include notes on alignment, shorts vs. ints, and indeed the merits of
> different colour depths.
>
> We could fill the section up with all sorts of things. Many people have
> trouble constructing decent timing systems for their games - we could
create
> a subsection on timing methods.
>
> We could also document different methods of screen update. I believe the
> docs currently direct people to the examples or the demo for how to do
this.
> This is where I would stop looking unless it's like 9:00 am on a Sunday.
> I've also noticed that many games do not maintain a constant speed
> regardless of fps - and it's really annoying when the programmer draws to
> the screen between vsyncs and your computer's too slow!
>
> I can think of a few other things that could go in. Basically it would be
> anything pertinent to game programming or optimisation, as long as it
didn't
> get too specific (so it wouldn't become like a universal handbook or
> anything). Tell me if you think this would be appropriate/a good thing in
> the Allegro docs.
>
> Ben Davis
>
>