Didn't AGS use Allegro (4)? At least it is mentioned on the legal page.
I thought I saw an Allegro DLL when playing Gemini Rue.

I like puzzle games and my favorite Allegro puzzle games include:

My own game, Deluxe Pacman which I created in the '90s with Allegro 2 I think at the time, and currently compiled with Allegro 4.4 has had over 1.6 million downloads from http://deluxe-pacman.en.softonic.com/ alone, not counting other websites. Not that I am terribly fond of it being on softonic but. Last month it had over 3300 downloads. It's just too bad I don't make any $$$ on them.

It can be downloaded (as well as a newer, as yet unfinished Deluxe Pacman 2, made with Allegro 5) from my personal homepage at http://home.cogeco.ca/~nroy15/games_index.html if you're curious.

Ha! (As in, I agree, not sarcasm.)

I had a moment of learning yesterday. I guess I never, or rarely had to change a passed pointer inside of a function and have that change propagate outside. So I found out the hard way about the purpose of pointers-to-pointers when my asset code was setting bitmaps yet not actually changing them. That sure was an odd change to track down. ("Is it set? Yeah it's set right here. Wait... why isn't it set?!")

I also apparently forgot again that polymorphism doesn't work without pointers... but all structures and algorithms compile and behave as if it works normally, just that the derived destructor will never be called leaving lovely obscure bugs.

On the bright side, I got my first Advanced / Modern C++ book in today (more still in the mail). Exceptional C++ Style. Basically, it should be titled, "You don't know anything about C++ at all, and I can prove it." Wonderfully well written and laid out concisely in a logical manner.

@taron, this is what I do.

void bumpbody_integrate(BumpBody * self, double dt) {
  if (!self) return;
  self->v_next = self->v;
  self->p_next = bevec_add(self->p, bevec_mul(self->v_next, dt));
}

BumpWorld * bumpworld_update(BumpWorld * self, double dt) {
  int index, jndex;
  /* simple integration for now. */
  for (index = 0; index < self->body_max; index ++) {
    BumpBody * body = dynar_getptr(self->bodies, index);
    bumpbody_integrate(body, dt);
  }
}

<sarcasm>Yeah, C++11 is much more clean and easy to understand that ANSI C... </sarcasm> Great illustration why I hate C++11 even more than C++98.

I believe in using whatever methodology makes the most sense for the problem, whether it's OO or modular, etc al, But yeah, that C++ seems more straight-forward. I did a simple Google for std::transform and understood the code and went "Hmm, that's pretty neat."

I wish I had the time to invest in learning boost (I'm also learning Modern C++ like generics, RAII, DI, and more at the moment). I've heard it's basically "C++ extensions everyone is already using while the C++ committee sits around debating them."

[edit]

This is interesting, Google's C++ style guide:

https://google-styleguide.googlecode.com/svn/trunk/cppguide.html

I initially had a lot of trouble reading the C too, but that's because I'm not really familiar with vector transformations and I had no idea what those obscure functions were... Of course, the second function isn't returning anything either.