Nearly done with PreparedStatement

It’s been a really busy week – starting out with me going locking down on Monday and working from home to get a whole bunch of stuff blasted out without having to go cowboy.

Somehow, inbetween everything else, I’ve managed to get a little ‘recreational coding’ out of the genuine need to get prepared statements integrated into the codebase for what we’re doing with the auth process.

So far, I only need data modifying statements, but the natural progression is a general encapsulation that will also support call/select etc. (Right now I never even both fetching the result set because none of my queries needs to).

FakeVector

Martini’s benchmarking seemed to be pointing a big hairy performance finger at some std::vector operations putting us in the need for a trivial array-based reference implementation of the vector to play with. Martini was set to go rewrite the surrounding code but I persuaded him to give me 3 minutes to rustle up a FakeVector template he could sub in for the STL version… Et voila…

And so it came to pass…

I really didn’t think this would happen so quickly. When you’ve been fitting spits and spots of systems together over 6 years towards a goal, you build up an overly active awareness of how much is involved. You’re overly inclined to fill in variables. I knew that the host was easy enough to build, and I’d scripted the mac build for Gophur, so I knew that wasn’t hairy. Recently I’d come to know that now the client and host source is all in one repository I can match source revisions. But, when I tried to put it all together, along with scripting it under Windows … Pop. I think my head just exploded, is that my amygdala on your lapel?

The key to it all was VSoft’s FinalBuilder. There are many build tools, but FinalBuilder is a basically a graphical scripting language / scripting language assembly tool the likes of which you expect from old Amiga tool sets or the Mac. These geniuses of it is delivering the power an old scripting hack like me only images getting from Perl/Python/Ruby/JavaScript/Rexx in a graphical interface.

Multiple inheritance

I’m not sure whether or not to be scared. I’ve been bleeding away dev time on the instancing work due to the lack of a standard definition of “The Player” between hosts processes. It was also a fairly large part of what kept me from delivering dynamic missions.

With no basal definition of a player within the system, who’s authoritative for any given item can be a nightmare.

So I had to introduce a new fundamental… class wwii::Player.

Vector initialization: Cross-platform gotcha

Well, oops; my fix for the map-crash bug broke the PC build. After a lot of head-scratching and some help from Ramp, he finally tracked it down to a crash in my new code, specifically in the RemoveSuperCells part of the destructor.