In VC, screen comes right after x/y in printstring.

printstring(x, y, screen, font, string);

And at the end of all other graphic function.

blit(x, y, image, screen);

I'm always putting screen in the wrong place. :D

It bothered me, but eventually I got used to doing it that way. ;_;

I'd fix it to use more conventional argument ordering, except... then pretty much all verge3 games would have a problem. Too bad there isn't function overloading for builtins (or anything).

Then you could have both of these:

// New way

PrintString(int x, int y, string text, int font, int dest);

// Supported, old, but deprecated way

PrintString(int x, int y, int dest, int font, string text);

Well, it's easy enough to make a MyPrintString that does it the normal way.

Quote:Originally posted by CrazyAznGamer

...And gives you more function overhead. ;_;
...>_>
Shut up. I'm like that.

It's a meaningless neurosis, like covering the toilet seat in toilet paper before taking a shit. VERGE is already so unbelievably slow that no amount of overhead matters.

And it should be noted that some of the current slowness is due to debugging type operations being turned on even in the released executable. I'm talking about bounds checks and the like. If you disable them and do some function inlining then vergec can be made to run like 20-30% faster. It's not huge but it's something.

Someday I might even commit my changes to SVN so that vergec is faster... That is once I find the end of this damned rainbow and once I see that blue moon I've been looking for.


Quote:Originally posted by mcgrue

It's not that slow, even. Sully runs okay enough on the GP2x, and the current version is running on only one of it's two CPUs. That's a 233mhz machine, btw.

Sure, there's room for improvement, but it's not "le terrible". At any rate, adding another function call to wrap a process is not costly enough to worry about.

You'll note that I said bounds checks in the released executable should be turned off by default. This is true. There needs to be a way to turn it on for when you are debugging but it's absolutely ludacris to leave it on all of the time. Bounds checking is a reasonably big slowdown, especially in vergec since it is interpreted. Turning it off loses nothing for the end user and, as a bonus, gives them a speed boost. This is a win-win situation.