search

SiegeLord / DAllegro5

D binding to the Allegro5 game development library
Other
42 stars 15 forks source link

Provide early feedback on a bad environment in the example. #31

Closed rcorre closed 8 years ago

rcorre commented 8 years ago

Resolves #30

SiegeLord commented 8 years ago

Merged with slight modifications as 731140d. I had a slightly more informative fix in the pipeline. Thanks!

rcorre commented 8 years ago

Cool, that extra version check should be a big help -- I've hit that myself a few times. Out of curiosity, do you know why the version string matters in al_init? I was working on binding another library (chipmunk2d), and noticed that I could, for example, use my 7.0.1 bindings with 7.0.0. However, with Allegro, the version string check means you need an exact match, which can be annoying if the difference is in parts of the API you aren't using. Is this intentional?

SiegeLord commented 8 years ago

This is a peculiarity of the 5.1.x versions. 5.0.x and in the future 5.2.x versions will behave in the way you expect. 5.1.x is the unstable branch, so it's allowed to change arbitrarily even for patch version bumps.

rcorre commented 8 years ago

Interesting, thanks.

On Thu 02/25/16 08:26PM, SiegeLord wrote:

This is a peculiarity of the 5.1.x versions. 5.0.x and in the future 5.2.x versions will behave in the way you expect. 5.1.x is the unstable branch, so it's allowed to change arbitrarily even for patch version bumps.

Reply to this email directly or view it on GitHub: https://github.com/SiegeLord/DAllegro5/pull/31#issuecomment-189109209