[no subject]

>    Yeah, my fix is for the newest CVS version or v4.1.9(WIP).  No fix 
> is needed for the current release version (which makes it hard to 
> maintain add-ons I might add)...  I guess I could redo it to detect 
> which allegro version is being used, but the current method of version 
> numbers is a tad confusing in my opinion... 4.0.3 and 4.1.9? <shrug>

What's confusing about it? It's the same versioning scheme the linux
kernel uses, and many other unix programs.

major.minor.revision

major = major changes in functionality
minor = not so major changes in functionality
revision = bugfixes, no change in functionality (usually)

there are usually 2 versions: a stable one (even minor revision) and
an unstable development version (odd minor revision). In allegro's
case, 4.0 is the stable tree, 4.1 is the unstable tree working towards
4.2, the next big stable release.

I can't find it in the documentation, but the following constants are
defined that you can use to check the version in your program:

allegro/base.h:#define ALLEGRO_VERSION          4
allegro/base.h:#define ALLEGRO_SUB_VERSION      0
allegro/base.h:#define ALLEGRO_WIP_VERSION      3

Hope that helps,
     Hein Zelle

>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< 
 Unix is user friendly. It's just very particular about who 
 it's friends are.

 Hein Zelle                     hein@xxxxxxxxxx
	                        http://www.icce.rug.nl/~hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<




>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< 
 Unix is user friendly. It's just very particular about who 
 it's friends are.

 Hein Zelle                     hein@xxxxxxxxxx
	                        http://www.icce.rug.nl/~hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<